To view parent comment, click here.
To read all comments associated with this story, please click here.
IMO the sweet spot for ASP is small to mid-range line of business apps. If you buy a control suite like DevExpress, you can slam together very high levels of functionality very quickly.
As soon as you step outside of that, it just becomes not worth it. Nowadays I am writing templated server controls for our in house designers to use. I do have a handle on the lifecycle, but unit testing anything we do tends to be 20x more complecated then the actual code.
Whenever I do anything in MVC, I just end up getting frustrated. I would use it over WebForms for anything other LoB apps in a heartbeat, but after learning rails and django there are things about it that just piss me off. Like the whole ViewData thing, the clunky code generation, the lack of any sort of persistence story for the model, and immature helper and validation story. The whole thing would have been less painful and alot more enjoyable if it had been designed from the ground up on IronPython or IronRuby
Edited 2009-04-03 19:53 UTC
Personally I love the ASP.NET model. ;-) It makes developing for the Web much more natural than any other model I tried.
I would brrrrrr if someone told me, all of sudden: forget the WebForm model - now it's all MVC...
Guess it's a matter of taste but I don't see any reason to move on now that Internet connections are getting faster and can support those huge ViewStates better ;-)




Member since:
2005-07-06
A bit clunky yes, but so much more intuitive than the page cycle based asp.net model which to this day (after 6 years or so of using it) still gives me fits. I always have a cheat sheet up in my cube outlining all of the page cycle events.