title: Best practise to migrate Web Forms to ASP.NET Core MVC
body: <p>I am trying to migrate a project from classic ASP.Net Web Forms to ASP.NET MVC.</p>
  
  <p>While I have read through <a href="http://www.codeproject.com/Articles/38778/ASP-NET-WebForms-and-ASP-NET-MVC-in-Harmony" rel="noreferrer">http://www.codeproject.com/Articles/38778/ASP-NET-WebForms-and-ASP-NET-MVC-in-Harmony</a>. I have a basic idea on how the code structure, libraries and routing should be done.</p>
  
  <p>For your information, the scope of my existing project is around 400 pages and 300 tables.</p>
  
  <p>On top of my head I have two approaches:</p>
  
  <ol>
  <li><strong>Start from stretch, rewriting the whole system</strong> - Obviously this would require intensive work and take a long time. Any change made on existing system would need a duplicate change made to the new system.</li>
  <li><strong>Migrate the page one each</strong> - I still have a rebuild the entire core library (for accessing db), and get the page migrated one by one. For this I  would assume to have two core libraries (new and old) running simultaneously with different pages connect to one of those.</li>
  </ol>
  
  <p>Would anyone have similar experience and advise a proper way to start?</p>
  
  <p>For this complete revamp I may also target at the latest technology - .NET Core and MVC6, by taking these would I have extra advantage, or some blockages I would have to take care of?</p>
  
  <p>Any suggestion and opinions are appreciated. Cheers.</p>