I have read all the post regarding the pro and con of ASP.net webform vs mvc.
However, I’m wondering under what circumstance does one use webform or mvc? would it come down to what you or your team is more familiar with?
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 have read all the post regarding the pro and con of ASP.net webform vs mvc.
However, I’m wondering under what circumstance does one use webform or mvc? would it come down to what you or your team is more familiar with?
Typical business application with lots of controls, their behavior rules, with enabling/disabling them in response to the events fired by other controls would be a lot more complicated task with MVC while with WebForms you can do it during a coffee-pause.
Also with MVC you get nice SEO-friendly urls out of the box, which is great for publicly exposed sites. WebForms do not offer that convenience, however, for internal applications or the public ones protected by customer login it is no concern at all.