Dino: ASP.NET MVC is MUCH better than MS seems to think

Dino Esposito, from whom many of us have read and learned a great deal over the years, has recently expressed his love for ASP.NET MVC.  Moreover, he has also notice that the message from Microsoft is very tentative about the framework.  Because of the large market share of Web Forms, Microsoft seems hesitant to push ASP.NET MVC as THE NEW VERSION OF ASP.NET for fear that existing customers will worry about being left behind.

I have previously predicted that with Visual Studio 2010, the majority of new ASP.NET projects would use the MVC flavor over the Web Forms flavor.  I stand by that because the IHttpHandler that is MVC is simpler to use and maintain than the System.Web.UI.Page (which is just an IHttpHandler).


ASP.NET MVC wins with simplicity, not features Posted on 11.11.2009 at 10:09 AM

Hot on the heals of DevConnections appearing to downplay ASP.NET MVC and folks like Dino Esposito taking notice , I want to provide my commentary on why the grassroots of the .Net developer community is so in love with ASP.NET MVC, even though Microsoft


Arnis L. said on 11.12.2009 at 2:54 AM

When i started to learn asp.net mvc, i noticed that Dino does not pay any attention to it (from blogposts). For me - it's (recent post by Dino) like a great confirmation to what i already knew => asp.net mvc IS better than webforms. Simple as that :).

Speednet said on 11.12.2009 at 2:54 PM

I respect your opinion, but you have to realize that for some of us, your argument sounds just like the same arguments people have been aspousing over the years for Microsoft to get rid of VB and go with only C#.

MVC might be easier for you, but I see no reason to change to a completely different model just because a few things may be a little easier (or not). Web forms are not difficult as it is.

Flying Dutchmen said on 11.20.2009 at 5:40 PM

I want to correct Speednet on his comment with reference to using VB in his argument.

If VB.Net was VB6 on .NET, hold the O/O, I don't think his argument would hold. The fact that VB.NET became an O/O environment means it is still around and a viable choice. Also mans it kept pace with the evolution.

So comparing ASP.NET to ASP.NET MVC, to me, is equivalent to comparing VB6 to VB.NET. Give me ASP.NET MVC, please.