title: Could not determine which version of ASP.NET Web Pages to use
body: <p>Weird goings on with my VS2013 projects.  I recently upgraded one of my project branches from .NET 4.0 to 4.5.1 and used NuGet package manager to install MVC 5 with Razor so that I could have a WebForms/MVC hybrid.  So far, it's working fine and I am able to use both WebForms and MVC.</p>
  
  <p>However, all of my other branches of the same project (the production branch for example) appear to be broken when they have not changed.  When I run one of the other projects, I get:</p>
  
  <p><code>Could not determine which version of ASP.NET Web Pages to use.</code></p>
  
  <p>After some looking around, I saw someone recommend putting this in the web.config appSettings:</p>
  
  <p><code>&lt;add key="webpages:Version" value="2.0.0.0"/&gt;</code></p>
  
  <p>Now when I run the project, I get this:</p>
  
  <p><code>HTTP Error 404.0 - Not Found</code></p>
  
  <p>What else is odd is that the URL is pointing to this:</p>
  
  <p><code>http://localhost:53305/Account/Login?ReturnUrl=%2findex.aspx</code></p>
  
  <p>I have no idea how making the change to MVC 5 in a different code branch could impact my other projects which are still straight WebForms using the 4.0 framework.</p>
  
  <p><strong>Edit</strong>:  It's probably worth noting that my other completely separate WebForms projects still work.  It's only the other branches of this particular project that appear to be broken.  It's almost as if there's some common configuration file shared between all of these branches that has been modified which ends up accommodating only the branch that was upgraded to MVC 5.</p>
  
  <p><strong>Edit</strong>:  In case how I installed the NuGet package is in question, here's what I did:</p>
  
  <ul>
  <li>Right-clicked my project and selected Manage NuGet Packages</li>
  <li>Clicked Online in the left pane and selected Microsoft ASP.NET MVC and clicked Install</li>
  <li>It did whatever it did and installed it for that project.</li>
  </ul>
  
  <p>I do not have this package installed in my other branches.  It's only a single branch.  Somehow, it affected all branches and I do not know why.</p>