ASP.net mvc 2 solution folder structure
asp.net-mvc, visual-studio
Solution
There's no best way. There are good and bad ways. Having everything in the same project is definitely not a good way. Big projects should be separated in layers and each layer usually goes into a different assembly so that it can be reused in other projects. For example you could have Models, Data Access, Business Logic, Web.
Jeffrey Palermo has a series of posts about the onion architecture which is worth reading.
From performance standpoint it is considered a good practice to have less bigger assemblies than many smaller assemblies.
Problem
What is the best way to organize a MVC2 web project (as complex as stackoverflow)? should i have everything in one project? if not, how should i separate the projects and folders?
Related problems
- asp.net mvc - subfolders
- What should the view file/directory structure be in ASP.NET MVC?
- Under an MVC framework, which directory structure would be expected by other developers?
- c# MVC - folder structure - where to put classes?
- Where should a ViewModel sit in the directory structure of an ASP.NET MVC application
- Changing ASP.NET MVC default folder structure