I am working on a DLL that I have a webservice service, I added new code and would like to compile and debug it through the NUnit test suite. I have taken the following steps:
Write my code in Visual Studio 2008 with the output directory pointing to the bin directory of my application (C: \ Program Files \ etc ...).
When I start the webservice process and join it, I get a warning that my program was built without debugging information, I found that if I copied the .pdb files to the directory C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\... , then I could avoid the warning, but still don't get into my code section.
I stopped my application, recreated my DLLs and ran the web application again.
After further verification, I noticed that when I stopped my application. process handler and deleted the subdirectory in the Temporary ASP.NET directory, and then when I restarted my process, the subdirectories get re-created, however they do not contain the new DLL that I just created, but the older version of the DLL, as well as the PDB files.
To summarize my question, how do I get Visual Studio to create and update DLLs in an ASP.NET temporary directory? For more information on how I can get Visual Studio to automatically copy PDB files to the same temporary directory without any batch help?
Ideally, I would like to avoid automatically copying my DLL to a temporary directory, but in my search today I could not find a suitable way to do this, since the internal ASP objects are completely uncontrolled.
NOTE. I have a shadow copy function when disabling NUnit when I hit my web service through an external executable.
source share