title: Why are my ASP.NET DLL's in "Temporary ASP.NET Files" not getting updated on rebuilds?
body: <p>I am working on a DLL that a webservice I have uses, I added some new code and would like to compile and debug into it via an NUnit testing suite. The steps I have taken are.</p>
  
  <ol>
  <li><p>Write my code in Visual Studio 2008 with the output directory pointing to my applications bin directory (C:\Program Files\etc...).</p></li>
  <li><p>When I launch my webservice process and attach to it, I get the warning that my program was built without debug information, I found that if I copied the .pdb files in the the <code>C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\...</code> directory then I could avoid warning but still not hit my code section.</p></li>
  <li><p>I stopped my application, re-built my DLL's, and re-started the web application.</p></li>
  <li><p>Upon further inspection, I noticed that when I stopped my application via. process explorer and deleted the sub-directory under the Temporary ASP.NET directory, then when I restarted my process the sub-directories get re-created, however they do not contain the new DLL's that I had just previously built but an older version of the DLL's, and no PDB files either.</p></li>
  </ol>
  
  <p>To sum it up my question is how do I get Visual Studio to both build and update the DLL's in the temporary ASP.NET directory? For more kudo's how do I get Visual Studio to automatically copy the PDB files to the same temporary directory without any batch assistance?</p>
  
  <p>Ideally I would like to avoid this automatic copying of my DLL's to the temporary directory, but through my searching today I could not find any suitable way to do this as the ASP internals are quite out of my control.</p>
  
  <p>NOTE: I have the shadow copy feature on NUnit disabled when I hit my webservice via an external executable.</p>