I am starting to doubt if there's enough benefit for dnnsoftware to work on MVC module support. I am only suggesting this in the case that their work on this support is taking away a lot of time and effort on working on vNeXt which is the full implementation of DNN in ASP.NET MVC. First, I think I read that the MVC modules will have some MVC limitations like not supporting partial views? Second, I don't know if the use of third party ASP.NET MVC controls will work properly in these type of modules. Third, is there enough benefit for current module developers? I am guessing that commercial module developers will not abandon WebForms modules to MVC modules. What's the benefit? It's not going to provide extra functionality which can't be accomplished using WebForms. This assumption is strengthened by the fact that DNN 8.x will be supported and enhanced even after vNeXt is out and therefore developers will just stick with WebForms until vNeXt is out and adapted. 

I would like to see vNeXt come out sooner than later and there's a TON of work for this to happen. If v8.0's MVC module support is going to be crippled or limited, maybe the question would be why bother with it and let us get full MVC support in vNeXt.

This discussion doesn't include SPA modules. I am assuming SPA modules can be done entirely in Javascript and the service framework without relying on WebForms nor MVC so this module type has its place.

Furthermore I would like to see a good list of MVC module limitations in v8.0. This will help developers thinking of new module development decide whether to stay with WebForms or use MVC in v8.0. I am one of them. 

Is it going to support partial views? A controller action which return PartialView?