ASP.NET MVC advantages over WebForms
I would never shit on another technology. I love WebForms, and have written dozens of Web Applications with ASP.NET WebForms framework 1.0, 2.0, 3.0, and 3.5. Some people like to jump on new technology simply because it's new or supports some new little feature people love.
I'm not on of those people.
I became a big fan of unit testing within the last couple years. And I've always been a big fan of SoC (seperation of concerns), which also enables and empowers simple unit testing.
So what are the big advantages of ASP.NET MVC that I love:
- View--Code-Behind approach does not abstract concerns the way it should. How many times have you, or a co-worker placed a ton of business logic into "btnSubmit_Click". ha ha. Funny, but true.
- ClientID. You want to create custom UI javascript. But you have to mix concerns by creating javascript in code-behind. Then calling a Page.RegisterScript
- MVC creates controls with the exact names as expected. Allowing you to maintain javascripts entirely in the views.
- Dynamic controls. How many times have you created dynamic controls in ASP.NET but it doesn't rebind as expected. So you rack your brain trying to figure out what's wrong, only to find out you're populating it before ViewState has loaded.
- MVC extracts model-binding from UI
- Routing URL's
- Built-in support for Json serialization
- Your presentation layer is unit-testable
- UI views can be re-used and based off your Business Entities (Models)
Friday, August 28, 2009 2:55:52 PM