title: ASP.NET website pages not reflecting recent changes
body: <p>I have been working on a new intranet site for a few weeks now, and everything has worked as expected.  If I made any changes whatsoever (added raw text, new controls, etc) to my .aspx pages, and then tested them in VS(F5), all changes would be reflected immediately in the browser.  Anything as simple as adding a <code>&lt;br&gt;</code> tag or as complex as adding a set of nested controls would show up upon a debug restart.</p>
  
  <p>Earlier today, everything was working.  Then I decided I wanted to play around a bit with some of the AjaxControlToolkit goodies.  I ended up installing the SP1 Update 2 for VS that was released today (<a href="http://www.microsoft.com/en-us/download/details.aspx?id=38188" rel="noreferrer">http://www.microsoft.com/en-us/download/details.aspx?id=38188</a>) while I was at it, as well as updating NuGet and installing the AjaxControlToolkit from there.</p>
  
  <p>I added a couple tools, including a ScriptManager and an UpdatePanel, and everything worked as I expected.  I then went to make a few changes, and added a second ScriptManager accidentally.  When I went to debug/run, it of course failed because you cannot have more than one on a page, so I removed the extra one and ran again.  It again gave the same failure.  I went through and made sure I didn't accidentally add another one somewhere, did a search on all files in my project and it was the only instance of it, so I commented it out and ran it again.  Same thing.  I tried a few things and ended up restarting IIS and VS and then the page behaved as expected.</p>
  
  <p>Since that point, any changes I make in ANY of my files in the project no longer update without exiting IIS and restarting it.  New, very basic aspx or html files in the project do the same thing.  I then reverted to the restore point before updating VS, and used a backup of my site from earlier in the day before I added the AjaxControlToolkit, and still, the problem persists.</p>
  
  <p>What is going on here?  I feel like its related to the VS update, but that doesn't really seem to make sense.  I can't see such a major bug being overlooked?   Why isn't IIS serving the updated page?  </p>
  
  <p>Ctrl+F5 in browser does not reflect changes.  Rebuild of entire solution does not reflect changes.  Closing and reopening browser does not reflect changes.  Changing my web.config does not reflect changes.  Creating a brand new empty web site and the problem persists.  Change to Visual Studio Development Server instead of IIS, problem persists.</p>
  
  <p>The only way I have found to force the correct, updated page to serve correctly is to "Stop Site" in IIS and then restart, which is simply way too much of a hassle to check minor changes to anything in my page.</p>
  
  <p>I am using Visual Studio 2012 Express, IIS Express, .NET 4.0, C# code-behind, files are on an intranet file system (mapped to x:), separate from my actual production hosting server.</p>
  
  <p>Just in case (though I don't think it matters since the problem is now occurring even with a fresh web site) here is my web.config (which is very basic):</p>
  
  <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt;
  &lt;configuration&gt;
    &lt;system.web&gt;
      &lt;compilation debug="true" targetFramework="4.0" /&gt;
      &lt;customErrors mode="Off" /&gt;
      &lt;httpRuntime /&gt;
      &lt;pages&gt;
        &lt;controls&gt;
          &lt;add tagPrefix="ttw" src="~/Controls/CustomerInformation.ascx" tagName="CustInfo" /&gt;
          &lt;add tagPrefix="ttw" src="~/Controls/CircuitInformation.ascx" tagName="CktInfo" /&gt;
        &lt;/controls&gt;
      &lt;/pages&gt;
    &lt;/system.web&gt;
    &lt;system.webServer&gt;
      &lt;httpProtocol&gt;
        &lt;customHeaders&gt;
          &lt;add name="X-UA-Compatible" value="IE=EmulateIE9" /&gt;
        &lt;/customHeaders&gt;
      &lt;/httpProtocol&gt;
    &lt;/system.webServer&gt;
  &lt;/configuration&gt;
  </code></pre>
  
  <p>Any suggestions would be greatly appreciated, and I hope a solution will aid others who may be experiencing the same issue after this most recent update.</p>