Best practice for structuring a new large ASP.NET MVC2 plus EF4 VS2010 solution?

Posted by Nick on Stack Overflow See other posts from Stack Overflow or by Nick
Published on 2010-05-18T17:27:18Z Indexed on 2010/05/18 17:30 UTC
Read the original article Hit count: 563

Hi,

we are building a new web application using Microsoft ASP.NET MVC2 and Entity Framework 4. Although I am sure there is not one right answer to my question, we are struggling to agree a VS2010 solution structure.

The application will use SQL Server 2008 with a possible future Azure cloud version. We are using EF4 with T4 POCOs (model-first) and accessing a number of third-party web-services. We will also be connecting to a number of external messaging systems. UI is based on standard ASP.NET (MVC) with jQuery. In future we may deliver a Silverlight/WPF version - as well as mobile.

So put simply, we start with a VS2010 blank solution - then what? I have suggested 4 folders Data (the EF edmx file etc), Domain (entities, repositories), Services (web-services access), Presentation (web ui etc). However under Presentation, creating the ASP.NET MVC2 project obviously creates it's own Models folder etc and it just doesn't seem to fit too well in this proposed structure. I'm also missing a business layer (or does this sit in the domain?).

Again I am sure there is no one right way to do it, but I'd really appreciate your views on this.

Thanks

© Stack Overflow or respective owner

Related posts about asp.net-mvc-2

Related posts about asp.net-mvc