Hi Guys,
I implemented the changes except for
Uncomment modules setting
<modules runAllManagedModulesForAllRequests="true" />
For now you will have to edit the web.config yourself to enable that.
My only other concern is whether that Activator.CreateInstance() might cause errors under medium trust. We need to test for that and if needed wrap error handling around it.
Michael's changes are changes to a plugin system I implemented to allow the possibility to plugin routes and routing which can be used with or without MVC. Currently this is not really use din any mojoportal features but it is plumbing for things I want to do in the future.
I'd like to re-iterate that mojoPortal is never changing to MVC.
These changes will allow you the possibility to use MVC for bolt on features or in supporting pages of CMS features. The FeatureModule itself I think would still need to be a UserControl. And using MVC for supporting pages of CMS features will pose challenges for visual integration since it would not use the skinning system. So I'm not sure MVC is feasible for use in CMS plugin features, but it could be used for bolt on features. Maybe you guys will prove me wrong.
What I mean by "bolt on" features is features that are not CMS plugins. For example my add on product In Site Analytics Pro is mainly a bolt on feature (though it does include 2 small cms plugins), it has a completely different ui than the main site and you access it from a link in the administration menu. This feature could have been implemented with MVC, I considered it but for expedience I went with WebForms. Bolt On features are the kind of thing you could build as a standalone app but by bolting it into mojoPortal you can at least still take advantage of a lot of mojo features such as roles and permissions and reduce overall development effort.
Best,
Joe