I’m making an Asp.Net MVC 3 project which should have about 10-15 views.
How should I decide if I should put them in one controller or many controllers?
Or is it a better approach to use one controller for one table of the database?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m making an Asp.Net MVC 3 project which should have about 10-15 views.
How should I decide if I should put them in one controller or many controllers?
Or is it a better approach to use one controller for one table of the database?
Separate your controllers logically. If you have something that is dealing with Products, make a Products controller. If you are dealing with an Account, use an AccountsController, etc.