by Albert Mutangiri
3. April 2010 03:32
I've been coding asp.net web apps using web forms for so long now, I mean since the early releases of .net framework and to be straight to the point webforms rock! Although this doesn't sound revolutionary, the fact that asp.net webforms makes building web applications quite handy by abstracting the complexities when dealing with things like application state, does this really mean we're all going to dump webforms for MVC??
Yes MVC is pretty sexy, it's a fix to the issues we have with web forms - refering to bloated ViewState and it's pesky postback model, so what happens when one needs an application state mechanism? Are we going to re-invent the weel? I really don't see the idea, this goes down to the idea of choosing the right technology for the right job.

70f97817-4228-408f-887c-2bfb42925383|1|5.0
Tags: MVC
ASP.NET