I am working on a large production SAAS Webforms application that is going to be slowly migrated to MVC 5. We want to be able to let some customers 'opt-in' to the new MVC pages as they are deployed based on a configurable setting.
The MVC application will be in the same project as the webforms application. The conversion to MVC will go feature by feature to basically create a complete MVC application standing side by side with the webforms application. Once all features are implemented and customers have converted we will remove the webforms project and keep only the MVC project.
If a customer 'opts-in' then we want them to view any MVC views that exist instead of the original aspx page. If an aspx page hasn't yet been converted to MVC OR they customer has not opted-in, then we want them to view the aspx page.
I have seen all kinds of posts and info about handling webform urls with routes, but the routing is still configured and loaded only once in app_start.
Where would be the best place to honor the 'opt-in' setting to send the user to the new MVC route instead of the legacy aspx page and what is the best way to implement this logic?
