Silverlight to ASP.net MVC migration
<p>I am tasked with migrating a Silverlight application to ASP.net MVC5. The challenge is that some of the modules have already been built in an MVC app that can run stand-alone or can load from within the Silverlight application. The existing MVC application has been developed over last 2-3 years by several developers of varying skillsets and the code is not in very good shape. The code has very poor coding standards adherence and poor re-usability, no coded unit tests, no DI, lots of inline styling, etc.</p>

<p>I want to start afresh with a new MVC project for the Silverlight migration so that I can try and address the issues in the current MVC app. Eventually, I want to reach a point where the Silverlight and the old MVC apps can be completely discarded and the new MVC app becomes the only one running. However, until the migration is complete, all three need to coexist. With the Silverlight application, I do not foresee a problem as I can tweak it to load the MVC pages from two different MVC sites. However, the main challenge I am facing is in figuring out a strategy so that users can access the new modules from the new MVC app from the old app until I migrate the old modules to the new app. It would not be feasible to make users access two different web apps for different features.</p>

<p>Some of the possibilities I have explored are, </p>

<ol>
<li><p>hosting the new application separately but loading the pages into iframes from the old MVC site.</p></li>
<li><p>using something like Razor Generator to precompile the new project and refer it from the old application.</p></li>
</ol>

<p>I am not very sure if the above are the best of ideas. I would greatly appreciate any suggestion to help me think and proceed in the right direction. Would also love to hear if there is a better/more appropriate approach to solve this problem.</p>