c:\inetpub\AAv6 (production – baseline & QW1)
c:\inetpub\AAv7 (UAT – QW2)
c:\inetpub\AAv8 (Dev – QW3)
Debugging v7 on my box was actually picking up the v8 version of SOME of the files (not sure if the v8 versions were put into the released binaries or the v7, primary (UI) binaries were v7 else I would have noticed a lot sooner). Primary offender was AAClasses.
This led to all sorts of “No, that can’t happen”, “Shit”, “That’s impossible”, “wtf”, “omg” & “huh?” behaviours.
1.) Close IDE
2.) Reboot (even w/ IDE closed (and killing all iis-related processes) there are still file locks on some of the dll’s & it was taking forever to identify these processes)
3.) DO NOT start IDE
4.) (didn’t help, but for giggles) kill the pdb files in the solution’s bin folders
5.) rd /s /q all dirs under C :\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\root
rd /s /q "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\root\"
a.) this will removed the cached binaries
b.) will make the first run of your project take forever so run through the whole thing once before you try to do any tracing/debugging
6.) Rename the root directory to make sure the ap does not find those binaries (Note – searching project and solution manifests revealed no references to the incorrect files)
7.) Test – you should now be playing with what you intended.