In my previous article I discussed developing a simple basic multilayered architecture for a .Net application. However there were a few points that I skipped since the article was for beginners. When we talk about an application architecture there are certain points that need to be clarified before proceeding; they are:

  • Is the architecture loosely coupled?
  • Is it to be service-based?
  • Where should the entities reside?
  • What should be the Mode of Communication with the database?
  • Does it require design patterns? If yes, What patterns should be implemented?
  • Should it be based on a Separation of Concerns?
To answer these types of questions, .Net 4 has come up with a generic solution, making use of the Entity Framework.

My effort in this article would be to put some light on building a generic multilayered architecture using Entity Framework 4.1 and the MVC3 Razor view engine. We'll use inversion of control to resolve dependency of layers. The points to be covered in this article would be as follows:
  • Use of Separation of Concerns,
  • Use of Code First approach,
  • POCO objects,
  • Repository Pattern,
  • Dependency Injection and Inversion of Control.

Read More...

I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to
C#,.NET,Architect,Intermediate,VS2010,.Net,Articles,Computer Tutorials,Entity Framework,Code First