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.
Possible Duplicate:
When should I create new Controller class in Asp.net MVC (Design Question)?
I’m relatively new to ASP.net MVC and I was looking into the code of some application. I haven’t given much of a thought for it earlier but when do we require a new controller? Are there any best practices regarding this?
This is probably a duplicate question – When should I create new Controller class in Asp.net MVC (Design Question)?…
…but, common practice is a new controller per resource, so for example, one for management of users, one for management of bookings etc. Then on each controller you’ll have actions for add, modify, delete.