>I think you mean it one solution containing multiple projects.
>
>Actually, that IS a best practice as a good way to split functionality for the application. For example, the MVC 4 app I'm working on has six projects in the solution: Database, Domain, Infrastructure, Services, WebUI, and UnitTests. These are all specific to this application, so they belong in one solution.
Yes, but should we include the framework project in all projects?