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.
What are the best practices when it comes to mapping controllers to views? For example, say for the urls mysite.com/login and mysite.com/register…I can have my LoginController and a RegisterController map to Login/Index.aspx and Register/Index.aspx views. Alternatively, my HomeController could handle both of these and map them to Home/Login.aspx and Home/Register.aspx.
Is one “better” than the other?
Login and Register seem like related actions that could be put in the same controller. An Account controller perhaps?
As far as better, I believe it would be easier to maintain one controller that handles similar or related actions rather than having multiple controllers. I’m not sure which is more accepted as being the “right” way to do it. Maybe just personal preference?