CODEWITHSUNDEEP
c#asp.net-mvcasp.net-mvc-4
Seth
Seth

Reputation: 984

MVC Controller Organization

I've inherited a project in which I'm the fifth proverbial 'cook in the kitchen'. The project is too mature for extensive changes on my timeline, but I'm thinking I can at least get rid of some of the "where was that code again!?" issues I'm having.

All of the controllers are dumped in the same Controller folder, but there are enough with similiar names to be a bit cumbersome. Additionally some of these controllers are solely for partial views. The admin page for instance has its own controller, but each of the four tabs on its view have their own model/view/controller. What are some recommended approaches I should take to get this under control?

Upvotes: 0

Views: 964

Answers (1)

Mister Epic
Mister Epic

Reputation: 16723

If you're looking to organize your MVC project, I find Areas an invaluable way to keep things from getting out of control.

It might mean changing some of your paths, but I'll leave it to you to determine the value to your particular project.

Have a read of this: http://msdn.microsoft.com/en-us/library/ee671793%28v=vs.100%29.aspx

Upvotes: 1

Related Questions