One of the things I find that makes MVC so productive is it doesn't have lots of control toolkits. Wrestling with grid databind events to make a row format correctly or chasing event handlers all over the place trying to work out if you need to use the OnShow, OnMakeVisible, OnEnable, OnPaint, OnDisplay event is a nightmare I am happy to see the back of.
On Mon, Mar 22, 2010 at 10:07 AM, DotNet Dude <[email protected]> wrote: > Bcoz webforms came to .net first and we all got productive with it. ;-) > Also webforms is more mature and lots of controls are available. > I have found that maintenance is faster with mvc though... very easy > to find bugs and unit test. > > On Mon, Mar 22, 2010 at 10:04 AM, Craig van Nieuwkerk <[email protected]> > wrote: >> Why not? >> >> On Mon, Mar 22, 2010 at 10:02 AM, DotNet Dude <[email protected]> wrote: >>> Hand coding html isn't necessarily a waste of time but I can't see mvc >>> development being as fast as webforms >>> >>> On Mon, Mar 22, 2010 at 9:55 AM, Craig van Nieuwkerk <[email protected]> >>> wrote: >>>> I don't think your an idiot ;-) But if you are someone who finds they >>>> can write HTML/CSS/Js much faster by hand than using the ASP.NET >>>> visual designers it shouldn't slow you down. But for people who think >>>> hand coding HTML is the biggest waste of time, you could be in >>>> trouble. >>>> >>>> Craig. >>>> >>>>> All I've found with asp.net mvc after using it for a few months is >>>>> that I can't meet my deadlines.... but maybe I'm just an idiot. :) >>>>> >>>> >>> >> >
