Clever Geek Handbook

Solution Framework and ASP.NET MVC Support

While building a restful ASP.NET MVC application, I'm wondering how best to structure the projects in my solution. By convention, controllers are in the same project as views. However, if I have several different view levels available for my quiet controllers, would it be better to put my controllers in a layer (project) lower than my views?

+1


source to share


2 answers


As I understand it, MVC controllers are an abstraction of page behavior and data access, but are still related to the views they provide. I am guessing that you can manage to pull the MVC controllers out of the project, but you will probably kill the benefit of removing duplicate code by making sure the controllers make the path to the common.



Edit: Your question is pretty much the same as this one .

+1


source


It looks like you are using MVC controllers to create a service layer that will be called by various other components in your architecture.



I would like to move this code to the "services" project and possibly use WCF to create services.

+1


source






More articles:


All Articles