After a lot of moon work, I show you our alpha version of our guidance V2.0. We are covering mainly the server side (just only a Silverlight client consuming it) evolving several experiences we have learned and putting into practice the feedback you have sent us.

Improvements in the Domain Layer
- Using EF 4.1 POCO Code-First for Domain Entities/Aggregates/ValueObjects
- Added more Domain logic within entities (no anemic domain)
- Better exposure of Aggregates’ elements
- Better support to navigations between Aggregates and elimination of inverse relationships not needed
- Entity Validation support
- Specification pattern implementation, use of expressions as specifications and composition support
Improvements in the Application Layer
- DTO and DTO-Adapters support
- Validation support
- Improvements in exception management
Improvements in the Data-Persistence-Infrastructure Layer
- Using EF 4.1, CodeFirst, DbContext
- Persistence layer simplification and improvements
- IoC: Elimination of abstractions no needed
- Better testing strategy for Integration Tests
Improvements in the Presentation Layer
- Reviewed and minor improvements in MVVM code
Improvements in the Distributed-Services Layer
- Segregation in 2 Web-Services.
- We will use REST in the next ALPHA/BETA version instead SOAP.

We got a lot of feedback coming from several channels as Discussions-Forum at Codeplex. We know that many followers are using this project (as a reference) into real & complex projects, with success in most of the cases. This is the best reward we could get!

Because we do bear in main your feedback, we have got many points we can improve. We will continue working and evolving both this guidance and sample in order to get better patterns’ implementations.

Thank you very much.

We finally get the English version of our 'DDD N-Layered .NET 4.0 Architecture Guide’ book which follows Domain Driven Design Architectural style and trends.

You can download this free book in several formats like PDF, EPUB,  and MOBI from:

https://msdn.microsoft.com/es-es/architecture/en/

We also provide an end-to-end open source sample application where you can check every .NET code aspect:

https://microsoftnlayerapp.codeplex.com/

We were working on it during 2010 and published the guide in Spanish in late 2010. It was awesome the excellent feedback we got and you can check it at our Codeplex site. We especially thank the Microsoft Entity Framework Product Group because they reviewed our guidance and gave us several improvements.

Goal

The goal of our guidance is to give our partners a .NET Base Architecture Guide that they can use as an outline for designing and implementing complex and mission critical enterprise .NET applications with long term life and long evolution. This book defines a clear path to design and implement business applications with a considerable volume of business logic. Following these guidelines you will get important benefits regarding quality, stability, and especially, an improvement of future maintenance of the application, due to the loose-coupling between components, homogeneity, and similarities of the different developments that will be done.

Technologies and Patterns

The guidance implements both typical DDD patterns  as Domain Entities, Repositories, Aggregates, Unit of Work, Value Object, Domain & Application Services, etc. and IoC/DI techniques, using the following technologies:

-Visual Studio 2010 y .NET 4.0, Entity Framework 4.0. Unity 2.0, WCF, Silverlight 4.0, WPF 4.0,  ASP.NET MVC 2 and 3,PEX & MOLES. Windows Server AppFabric Hosting & Cache (Optional). Windows Azure (Optional), SQL Server, SQL Azure (Optional)

Future steps

This guidance is a living Project so it will continue evolving the Guide and Sample App. Specifically we are already working on the following new features:

- EF 4.1 evolution (POCO Code-First Entities)

- Claims-based Security implementation on the sample application (The Guide already covers it)

- New Client technologies (Windows Phone 7, HTML5, etc.)

We hope this work might be useful for many organizations and we encourage you to provide feed-back and new ideas using our discussions-forum at Codeplex.

Miguel Angel Ramos

Application Development Manager

We’ll give a printed draft/beta version of this proposed Architecture to all attendees.

Some clarifications of my folk Cesar de la Torre:  Note that this proposed Architecture is based on DDD (Domain Driven Design) Architectural Styles and SOLID principles …it is made for complex apps where you have a lot of business/domain logic and also it is an App with a long-live where you want it to be protected from technology changes that could occur in the future...

I wish you 0 error coding!