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

I would suggest following a Domain Driven Design (DDD) and one suggested way of laying this out would be creating the following projects:

Company.Project.Web <-- Your MVC Application, though you can still use WebForms Company.Project.Domain <-- Data Transfer Objects (DTO's), ViewModels, Business Logic, Events Company.Project.Data <-- Repository Interfaces

Company.Project.Data.EF <-- EntityFramework Specific Implementation of Repositories Company.Project.Model <-- Your EF CodeFirst Classes

Company.Common <-- A common project of utilities and/or extensions

I would suggest you take a look at Project Silk http://silk.codeplex.com/ from the patterns and practices team. Great reference implementation of DDD, Repository, and MVC as well as mixing in HTML 5 and jQuery (vNext).

Answer 2

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.