Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Since i started learning MVC i've grown to hate webforms. The idea of webforms has been to abstract everything so it looks like a winforms development environment, there really is a lot of butchering. You don't have this with MVC, the request handling process is much more natural and you actually get to see exactly what the server is doing. It removes all the numerous page events leaving you not always 100% sure what's going on behind the scenes.
As others have said. You also get a lot move control over the HTML you are producing which is very helpful if you have rich client sides using a lot of AJAX, JQuery etc.
Granted for quick and cheerful websites it's probably going to be quicker to use Webforms. For larger projects though, i think it pays off in the long term to use MVC.
If you've got a database and need a few front-end screens for it and don't really mind how they look as long as they do the job, it's a huge labour-saver.
If you know what you want your web pages to look like and then do a top-down design, it's quite painful.
Comment