Timeline for When to favor ASP.NET WebForms over MVC
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 21, 2015 at 8:33 | history | edited | Tjaart | CC BY-SA 3.0 |
corrected spelling and grammar
|
| Dec 27, 2014 at 6:37 | comment | added | angularconsulting.au | @Tjaart It is not quite right that you cant have multiple forms on ASPNET page. You could have as many forms as you want in ASPNET page but you could have only one server form - form with runat="server" attribute. | |
| Dec 23, 2014 at 2:04 | comment | added | Nelson Rothermel | @mjb: If you don't use server controls, ViewState and so on, why use WebForms at all when MVC is closer to what you're doing? It's like driving a tractor to work but not doing any offroading or using the shovel/hoe or stabilizer bars. At that point why not just use a car? | |
| Jul 30, 2014 at 10:09 | comment | added | mjb | But, however, IMHO, for programmers of WebForm, you are strongly recommended to learn MVC which makes you an even more better WebForm developer. | |
| Jul 30, 2014 at 10:02 | comment | added | mjb | You can have plain html controls in WebForms, no one force you to use Server controls. You can have full stateless Webform, no one force you to use ViewState. You can use full ajax and jQuery in Webforms, no one is restricting you from using jQuery. You can implement URL routing, no one force you to use static file base URL. Manually drawing a page with CSS consume the time as much as MVC needed. You can design HTML page directly on Webform. | |
| Mar 2, 2014 at 11:25 | comment | added | Vishal Sharma | @answerer , you haven't pointed out the most important , test driven development with asp.net mvc is very easier,, and does it possible to do the same with asp.net ? | |
| Jan 17, 2014 at 17:37 | comment | added | Andy | I have to agree 100% with this answer. At the end of the day, WebForms makings doing things on the client side (html / browser) so much harder. You literally have to fight the framework to get somethings done. An aspx page ends up with so much more code due to server controls than a cshtml page typically does. @šljaker If you start turning off ViewState and avoid server controls, you've abandoned much of WebForms at that point. I don't see that argument as particularly convincing. | |
| Jan 5, 2014 at 18:51 | comment | added | Mahmood Dehghan Tazereh |
As a developer who did some huge apps in WebForms and some good ones with MVC, I agree with most of the things in this answer. especially #8: ASP .Net WebForms is not only an abstraction over html, it is an extremely complex one ...
|
|
| Dec 18, 2013 at 12:18 | history | edited | Ian | CC BY-SA 3.0 |
spelling
|
| Dec 17, 2013 at 9:59 | comment | added | DarrylGodden | There's so many untruths in this answer I'm surprised it has 41 up votes. | |
| Nov 27, 2013 at 22:59 | comment | added | šljaker | The most of things you mentioned here are not true (but I won't give you a downvote). Nothing prevents you to turn off the viewstate in WebForms and use ViewModels and if/for loops instead of data binding and server side controls. | |
| Apr 3, 2013 at 14:42 | comment | added | jao | +1 for pointing out multiple forms. Plus the fact that the HTML webforms generate is most of the time not very SEO friendly (as in: large chunks of viewstate on top of the page) | |
| S Oct 19, 2012 at 7:33 | history | answered | Tjaart | CC BY-SA 3.0 | |
| S Oct 19, 2012 at 7:33 | history | made wiki | Post Made Community Wiki by Tjaart |