title: Why did the order of Areas in RegisterAllAreas change with Visual Studio 2015?
body: <p>After installing Visual Studio 2015 on multiple machines, the order of routes in the routemap picked up by AreaRegistration.RegisterAllAreas() seems to have reversed itself. </p>
  
  <p>I have 3 areas in my application, each of which has its own AreaRegistration implementation and registers its own specific route. </p>
  
  <p>On machines with only Visual Studio 2013, the list of routes (as reported by the RouteDebugger plugin) was:</p>
  
  <pre><code>SomeArea/{controller}/{action}/{id}
  DifferentArea/{controller}/{action}/{id}
  {controller}/{action}/{id}
  </code></pre>
  
  <p>On machines with Visual Studio 2015 (and the exact same source code)</p>
  
  <pre><code>{controller}/{action}/{id}
  SomeArea/{controller}/{action}/{id}
  DifferentArea/{controller}/{action}/{id}
  </code></pre>
  
  <p>This was causing 404 errors because the more general route was now matching routes that it did not previously. Why would the order in which the areas were scanned for their AreaRegistration classes change with the installation of a new version of Visual Studio?</p>