View Single Post
  #29 (permalink)  
Old June 16th, 2011, 03:21 PM
Lee Dumond's Avatar
Lee Dumond Lee Dumond is offline
Wrox Author
Points: 4,942, Level: 29
Points: 4,942, Level: 29 Points: 4,942, Level: 29 Points: 4,942, Level: 29
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jan 2008
Location: Decatur, IL, USA.
Posts: 923
Thanks: 12
Thanked 166 Times in 162 Posts
Default

Well, I mention this because one of the original objectives of WebForms was (and still is) to abstract away things like the request pipeline, markup, design, and so forth. If one doesn't have strong knowledge of those things, then that is an argument in favor of WebForms. That being said, if one doesn't have that knowledge, maybe that person shouldn't be programming for the web in the first place.

In response to your comment, I would maintain that using WebForms to "quickly achieve a simple clear cut urgent business objective" is a straw man argument. With the MVC scaffolding tools available in Visual Studio there is absolutely no time advantage in using WebForms at all. None whatsoever. And once you get beyond very basic CRUD operations, the time spent in fighting the WebForms abstractions quickly becomes a time-suck in itself. I can honestly say that MVC lets me be far, far more productive than WebForms ever did.

And nobody, especially me, is claiming MVC is original to Microsoft, or is a "magic bullet" of any kind. Bit it IS a vast improvement over WebForms in virtually every way possible. I don't think there is much argument over that.
__________________
Visit my blog at http://leedumond.com
Follow me on Twitter: http://twitter.com/LeeDumond

Code:
if (this.PostHelpedYou)
{
   ClickThanksButton(); 
}