ASP.NET and MVC: Most Viable Solution?
August 23rd, 2007
The following is my response to ScribeSonic’s article on MVC & ASP.NET. The author discusses the different frameworks that are currently available and which is the most viable solution.
I’ve used Monorail on a couple projects now. I feel so much faster working with a pure MVC implementation than I did in classic Web Forms. However, Monorail is most likely going to get the ax by our CTO due to the learning curve required for a) the MVC framework, and most importantly b) having different view engines and losing support for web forms development, page lifecycle, and third-party controls. Point (b) is one of my favorite features of Monorail, but our CTO brings up a good point in that we don’t have time to retrain EVERYBODY on a new framework with a completely new train of thought.
According to the codebetter.com article linked above, the Microsoft MVC implementation will allow for true webforms usage. This will be the single greatest feature that makes companies decide upon the MS implementation vs. Monorail or ProMesh.Net. Companies today don’t have the time or interest to retrain an entire dev team away from everything they’ve been learning for the past five years. It’s a tough situation, and while I love and will continue to support Monorail as much as possible, I’m not sure it’s the most viable option for companies that are already knee-deep in Web Forms code.
- Posted 10 months ago
- Permalink
- Digg This!
