Object role stereotypes can help you better understand and clarify the responsibilities of the objects in your application.
MSDN Magazine August 2008
View Complete Post
Jeremy Miller explains how internal Domain Specific Languages can help you craft code that is easier to read and write. His bag of tricks to improve your programming includes extension methods, fluent interfaces, object extensions and use of the semantic model.
MSDN Magazine January 2010
This article examines how the new support for functional programming techniques in .NET 3.5 can developers make code more declarative, reduce errors in code, and write fewer lines of code for many common tasks.
MSDN Magazine October 2009
The end goal of software projects is to deliver value to the customer. Software design is a major factor in how successfully a team can deliver that value. The best designs are a product of continuous design rather than the result of an effort that tries to get the entire design right up front. This approach lets you strive to apply lessons learned from the project to continuously improve the design, instead of becoming locked into an erroneous design developed too early in the project.
MSDN Magazine August 2009
Jeremy Miller continues his discussion of persistence patterns by reviewing the Unit of Work design pattern and examining the issues around persistence ignorance.
MSDN Magazine June 2009
Here we examine data persistence patterns to help you determine which best suits your needs. We look at a number of patterns, including the Active Record, the Data Mapper, the Repository, the Identity Map, the Lazy Loading, and the Virtual Proxy.
MSDN Magazine April 2009
We look at some techniques you can adopt to reduce the amount of housekeeping code you write so you can focus on the essence of the application.
MSDN Magazine February 2009
Designing testability into your app means smaller tests that are cheaper to create, easier to understand, faster to run, and much simpler to debug.
MSDN Magazine December 2008
Here are some design patterns that allow you to achieve higher cohesion and looser coupling for more flexible, reusable applications.
MSDN Magazine October 2008
Extending an existing codebase can be as productive and frustration-free as writing all new code when you employ the Open Closed Principle. We'll show you how.
MSDN Magazine June 2008
I have been using properties and have idea that using properties with private fields we can implement validations and buisness rules in them.
But I am just thinking asp.net client side validation controls provide good strength and they provide good user experience as well. They can be used for any type of validation (using regular expression) on client side and their re-use is possible on server side. When validation controls are a must and they are powerful; is making properties not just wastage of time ?
Is there still some use of properties ? Please guide me.