Basically what is being proposed is a way to designate a tab inside DNN as a MVC content page instead of WebForms.
The existing WebForms style system would continue to work for all existing pages and things like admin and host menus
- but if a developer wants to build part of their site using MVC then they can assign pages/tabs to run as dedicated MVC.
The developer gets all the advantages of the DNN framework in terms of menu systems and the underlying dnnapi core,
with all the functionality they expect of MVC for their own coded content.
There are likely to be some caveats as I understand it
- traditional dnn modules based on ascx and webforms wont be able to run on the MVC page
- MVC modules wont be able to run on webform pages
- and the skinning for the MVC pages will be handled by Razor and as such may not be directly compatible with existing DNN Skins.
On the up side - there is as part of the proposal a suggestion for new HTML5 style client side module that would be compatible with both MVC and WebForm tabs.
Westa