For developers: ASP.NET MVC vs. WebForms
This is a question that has started a lot of heated debate in the web development world. Like most such question there’s no right or wrong answer – it all depends on your particular project requirements, functionality and experience.
If you team has strong background in WebForms, maybe the cost of learning a new technology may not pay off, so you should stick to plain old WebForms.
If you like to have minimalist HTML output and complete control over the markup, then maybe you should start using MVC.
We cannot give you any advice, because each case is so specific. We advise you to always know your options and evaluate them when you start each project. Our job is to provide options for everyone and let you use the technology that you know best. We’ve done this with the introduction of MVC support, but we don’t want to convey a wrong impression that you should immediately move all your assets to it – that could be expensive and useless.
We trust that developers know best, and would always recommend a good practice over a bad one, but there is no good and bad in the case of WebForms and MVC. What we can give are some cases where using one of the options would be easier.
- Porting existing MVC applications to Sitefinity
- A need to use Telerik MVC extensions
- A team with very good MVC skills
- A need for clean markup and heavy client functionality
- Porting a legacy application that uses WebForms to Sitefinity.
- A team with very good WebForms skills
- A need to use RadControls for ASP.NET Ajax
- A need to use postbacks and control lifecycle with no client functionality
You can use those for guiding principles, but should not follow them blindly. Evaluate your objectives and choose the technology which lets you achieve them quickly and easily.