To the developers thinking about using MVC in DNN 8+, from my personal experience the DNN MVC support is crippled. I couldn't use it when I tried to create a prototype using the third party MVC extensions I wanted to use. DNN simply doesn't support the full spectrum of partial views which is an integral part of ASP.NET MVC. It was a road block. You can either use the standard WebForms which Microsoft continuous to support and will support for years ahead. They are just a ton of WebForms web apps around. MS will not abandon the technology any time soon.
However if you are starting fresh and want to use something newer, skip MVC and use Javascript and any of the JS frameworks and any JS based UI controls. Telerik, DevExpress, Infragistics and ComponentOne offer both ASP.NET WebForms and JS/HTML based UI components. Or any JS UI component since they are not dependent on the backend technology used. They only need to talk to an API like teh SPA framework in DNN.
The advantage of using a JS/HTML front end is usually they also work very well for a mobile device if they are using responsive design principles.
The drawback is that you might be writing a lot of javascript code. To alleviate some coding pain, I suggest using Typescript which supports strong types and object oriented principles like class and inheritance. You can have Typescript output classic ES5 Javascript which is compatible with all the browsers. Angular 2 is out and it strongly uses Typescript therefore you probably can't escape learning Typescript. All the ng2 examples I have seen use Typescript.
Personally I suggest dnnsoftware concentrates its efforts into the SPA framework. The MVC support is more like a hack and if it doesn't support the full ASP.NET MVC functionality then why bother. You will get very frustrated if in the middle of your development project you wanted to use a critical ASP.NET MVC functionality and find out it doesn't work in DNN. It will be a big waste of time. Just do the development in WebForms or the newer SPA. Stay away from DNN's MVC. I wasted about 3 months trying to get it to work for my needs. Granted I was working on the RC versions. I got excited for nothing. It was a frustrating experience. The worst part is when you seek help in the forum and no one answers for the simple reason that very few developers are using MVC in DNN module development and understand what's going on. You're on your own. There is ZERO advantage of using MVC in DNN. I hope this message gets across to would be developers.
I keep hearing the message from dnnsoftware that they support ASP.NET MVC when the true story that the support is full of potholes. I also feel sorry for the forum posters who are seeking help in the forums for MVC. If you can an error you can't explain, it's probably because of DNN's wonky MVC support.
To be honest I wish they remove MVC support from DNN 9 so people don't fall in that trap. Two options only => WebForms and SPA.
Later when DNN is truly built on MVC using ASP.NET Core, if they every go there, then it can say it supports ASP.NET MVC.
I will post this as a blog comment and put it in the forum. I want this message to spread.