Best Structure for ASP.NET MVC Solution
问题 I tried to structure my last sizeable MVC project following a best practice approach, but didn't quite understand what I was doing. It has a Data, Business and Web (MVC) project, but the controllers contain most of the code, the Data layer uses NHibernate and has a few repositories responsible for too many things, and the Business layer is a dumping ground for anything that doesn't belong in the other two projects. It works, but I feel it could have been setup better - the main things I'm