Whats a recommended solution structure for a somewhat large website in asp.net

Question

Im currently trying to refactor a project(asp.net mvc) that doesnt have any separation at all. just folders :s

• The project has a bunch of EF Code First classes (Pe

Answer 1

We use a similar design to that mentioned by jdmonty but a bit simpler. We do the following:

• ApplicationName.Web - MVC Application
• ApplicationName.Services - Business logic
• ApplicationName.Domain - EF CodeFirst classes and the repositories that act on them
• ApplicationName.Common - Classes and utilities used by multiple projects
• ApplicationName.Tests - Test for the various projects

The Web project is dependent upon the Services project. The Services project is dependent upon the Domain project.