Browse by Tags
All Tags »
Architecture (
RSS)
Just the other day, I had an argument about the way to add references to a project. As you already know, there are two main ways to achieve that: Project Reference. File Reference. The “Project Reference”, add a reference to a project within the given solution where a "File Reference” references an assembly that is located everywhere, either on the local machine or on the network (we just browse to it and add it to the references). So, the question is: “when to use Project and when to use File...
Grigori Melnik, who is the PM for EntLib over in Patterns & Practices, posted about planning version 5.0 features. According to Grigori and I quote: "We’ve started our planning of the Enterprise Library 5. This is your chance to send us suggestions, comments, screams... These may include ideas for new blocks, new providers for existing blocks, integration with new .NET Framework 4.0 features, improvements to the design-time experience, performance improvements, support of specific deployment...
I am off to a customer that is located at England. I am going to support the customer in the process of migrating to Team Foundation Server. Now let me clarify that. Migrating to TFS is not only about installing the server and migrate to Team Source Control, it is much more. Yes, installing TFS is much easier than it was on the 2005 version, and in most cases a well capable system administrator can perform do it by himself. So, why choosing us? The job of migration include many aspects, the most...
Here is a quote from a book I am reading now: "To eliminate the need for a branch entirely, automatically migrate your customers and users to the latest version every time you release." But wait, was is a branch? Branch Simply put, to branch your code is to split the repository into two separate lines of development. You can branch by release, feature, product and so forth. Back to the first sentence... This book I am reading is "The Art Of Agile Development", which talk about...
Have you ever seen this code: class Program { static void Main(string[] args) { Person p = new PersonManager().GetPersonById(1); } } class PersonManager { public List<Person> People { get; set; } public PersonManager() { People = new List<Person>(); } public Person GetPersonById(int id) { Person res = (from p in People where p.Id == id select p).FirstOrDefault(); return res; } } class Person { public int Id { get; set; } public string Name { get; set; } } Take a look at the GetPersonById...
J.D Meier recently posted about new application architecture pocket guides. Agile Architecture Method Pocket Guide A new guide has been released by the Patterns & Practices team This guide describes an approach for agile architecture design and presents an overview of the approach, explains the main activities and how to adopt them. Here are the chapters: Introduction Chapter 1 - Agile Architecture Method Chapter 2 - Step 1: Identify Architecture Objectives Chapter 3 - Step 2: Identify Key Scenarios...
How would you define success in your software development? No matter which methodology you use, it can be either Agile or Waterfall or CMMI, they all trying to make you successful in developing you software. The traditional idea of success is delivery on time, on budget, and according to specification. A Successful project will be one the is “Completed on time, on budget, with all features and functions as originally specified.” (from The Art Of Agile Development). When your project is missing with...
We have all heard that Linq To Sql is dead. I even posted about it here: You Are The Weakest Linq, Goodbye! Stephen Forte , just posted another confirmation on our dead patient. So, what should you, me and hundreds more companies that are using Linq 2 Sql do? According to Stephen: So what should the Linq to SQL developer do? Throw it all away and learn EF? Use nHibernate? No. The Linq to SQL developer should continue to use Linq to SQL for the time being. If the next version of the EF is compelling...
S.O.L.I.D. is a collection of best-practice object-oriented design principles that you can apply to your design to accomplish various desirable goals like loose-coupling, higher maintainability, intuitive location of interesting code, etc. So what are the principles? There are five principles of class design. They are: SRP A class should have one, and only one, reason to change. The Single Responsibility Principle PTOM: The Single Responsibility Principle by Sean Chambers POTM: The Single Responsibility...
Windows Azure Tools for Microsoft Visual Studio extend Visual Studio to enable the creation, building, debugging, running and packaging of scalable services on Windows Azure. Windows Azure Tools for Microsoft Visual Studio includes: C# and VB Project templates for building Cloud Services Integration with the Development Fabric and Development Storage services Debugging Cloud Service Roles running in the Development Fabric Building and packaging of Cloud Service Packages Browsing to the Azure Services...
David Chappell has put together a white paper that provides an early look into how your application architecture changes with the introduction of Azure Services Platform . David explains and talk about: Windows Azure .NET Services SQL Services Live Services You can download his white paper here .
PDC videos are now available in channel 9 . Some sessions I have set myself to see are: The future of unit testing Team foundation server 2010: cool new features WCF: Zen of performance and scale Improving .NET performance and scalability Entity framework features WF 4.0: first look The future of C# Architecture without big design up front Agile development in visual studio There are a lot of other cool sessions. What do you find interesting?
Jeremy Miller posted a new article on the core concepts: Cohesion & Coupling. I read it and suggest you all to read it as well.
Reports are usually a common requirement when building a software. So, in order to allow to view reports, filter them, build new report and etc. we must first decide on the technology we will use. In order to do so, we first must understand the requirements. Requirements for the reports vary from one application to another, but still there is common ground to all. Here is a list I found out to be common in several cases: Localization & Multi Culture. Security. Report Composition. Formatting....
In my previous post "Design Decision: Where to place the admin for your application" I have explained a design decision I had to take. Generally, I was looking for a solution on where to build my application administration. Alik Levin , suggested that the administration should be placed on a different process (application) from the main process (application). His main motivation is security. I must admit, usually I would agree with Alik, however there are several more considerations that...
More Posts
Next page »
