A better webforms?
Last week Phil wrote about the concerns of webform developers that Microsoft was leaving webforms behind in favour of the MVC framework. As Phil writes that is clearly not the case and webforms is enjoying a lot of technology cross over from the MVC framework, which brings me to my post. What I don't want is another webforms\MVC framework flame throwing war (since such things serve no one), what I do want is for webforms to enjoy more of this cross over, be a better framework and let me go home on time at night. As we all know webforms does not lend its self well to certain models of development, its concerns are mixed; TDD and SOC (MVP patterns for example) are clumsy. You might say "we have MVC for that..." but the biggest problem is one of the investments in style, skills, technology and time that a business has put into webforms and it not sticking to the MVC way. Webforms can still be webforms but what I'd like to see is a little more cross over so that all time and money is not wasted but you can use (or not if so wish) your own style of software engineering. What springs to mind beyond what MVC has already given is...
-
Webforms use the MVC view engine.
-
SOC for the code behind, just a plain old class please.
-
SOC for everything else, testability and mockability everywhere.
Now if I had a plane ride due I'd likely just hack up the view engine and build my own but food for thought all the same, what's your take?