Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen and why should I consider asp.net MVC?
    text
    copied!<p>I've noticed a lot of talk about asp.net MVC lately, but I haven't come across a clear or compelling description of when, where or why I would want to use it over WebForms.</p> <p>Let's say I wanted to build a small web application that allows a person to advertise some items online. The website will have 4 use cases: </p> <ul> <li>Search adverts </li> <li>View listings </li> <li>View item </li> <li>Place an advert</li> </ul> <p>Let's assume:</p> <ul> <li>I'm not particularly interested in unit testing my controller. The page will either render the list of items correctly, or it won't. </li> <li>I am interested in more control over the HTML markup.</li> <li>I'm not interested in using the latest buzz technology just for the sake of it.</li> <li>I am interested in using the tool that is best suited to the job in terms of productivity, performance, maintainability &amp; simplicity of the end solution.</li> <li>I don't want to have to work around a bunch of nuances to get something simple to work.</li> </ul> <p>So, my questions are thus: </p> <ul> <li>What are the fundamental differences between the two models?</li> <li>In which scenario is one better than the other?</li> <li>What are the gotchas with asp.net MVC (I'm aware of the gotchas with WebForms)</li> <li>For our sample app, what would I gain by using asp.net MVC instead of WebForms?</li> <li>For our sample app, what would I lose by using asp.net MVC instead of WebForms?</li> <li>Is it feasible to mix and match models within the same small application?</li> </ul> <p>Thanks to anyone who spends the time to contribute an answer.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload