Dec 17, 2007 04:14 PM|abombss|LINK
I may be going out on limb here, but I am guessing you have lots of code in the code-behind of your regular aspx pages?
If you do, how are you testing that?
How are you sure you do not have business logic leaking in code behind?
Simple scenarios like coloring a table row if a value is negative is pretty complicated and can only be done in code-behind. In mvc things like this are very trivial. I don't want to write code for presentation, I want to write views and templates.
Lines of Code, to me is one of the worst metrics for assessing if a technology or platform is the right one or not. Just because its less code does not mean its easier to maintain or extend. If you are happy with webforms stick with that.
I haven't used webforms by choice in over 18 months because I found them to just be too difficult to work with. I found myself always fighting the framework to make things I wanted to work.
I also wanted real lightweight ajax without dealing with postback and full page renders, etc.
Again, back to testability, I also struggled with testing my webform code, and over time I always started to leak things into my code behind that should not be there. MVC is the right approach for me.
Obviously loc is a factor but testability, maintainability, solubility, loose coupling, are more important in my book and I have found MVC frameworks much better at achieving those goals than webforms.
With tools like ReSharper I worry less and less about lines of code as I can have templates, snippets, and total control over refactoring.
Just my .02