Scott shared today on some changes coming to the asp.net mvc release candidate.
I. He starts with the option (default now) of â€˜no-code behindâ€™ pages. Very nice!
(Iâ€™m not sure how this will work with generics (ie. a simple view of IList<Things>)
Personally I think this is a great move. 99% of my files donâ€™t have code behind â€“ and the only ones that â€˜didâ€™ were refactored (I had used a repeater on a few pages, then later replaced with the MvcContrib Grid)
II. The HTML/Ajax helpers will now enable expression syntax.
Iâ€™ve been doing something similiar lately after examing how the MvcContrib Gridview was built, in order to do other controls with jquery, ie. TabViews, Treeviews, etcâ€¦
I hope and think that this will greatly speed up the development of those controls.
III. Scaffolding support
This one looks interesting â€“ definitely check it out. At the very least, I see it as a RAD capability, that would then allow easy modification if needed.
IV. MSBuild Tasks for the View
(Hey Ryan!) â€“ this is excellent news! Iâ€™ve told my friend Ryan several times – â€˜I wish the build would pick up on any html helper errorsâ€™. This will save a ton of time, as it wouldnâ€™t be until runtime that a problem would be spotted (although Resharper was good as picking it up – *if* you saw it â€“ lol)
So, looks like more goodies, the framework begins to flush out a bit â€“ looks all good â€“ and nothing that appears to be major breaking changes (whew). But weâ€™ll seeâ€¦ the cost of doing MVCâ€¦ 100% worth it.