Have you had the problem of making changes to a dll in Visual Studio, doing your build, referencing that changed dll in another Visual Studio instance and viola! the new changes are nowhere to be found. Visual Studio intellisense has no idea about the new changes, and it wont build either???
How can this be? I just overwrote the dll with my new one and somehow it’s not there??? Well friends (and I do use that term loosly) I have your solution. It seems that Visual Studio has a built in Shadow Copy feature. It was put in there for just this situation, to screw things up with references when we are being most productive, but I digress….
Here is how to solve the problem ( This also solves the license problems of some 3rd party controls, read about that here):
I went into the temporary files (mine are at C:\Documents and Settings\jeff\Local Settings\Application Data\Microsoft\VisualStudio\8.0\ProjectAssemblies) and I deleted all of the folders in there. You may have to unhide these folders in your explorer tools -> folder options -> view tab and you may have to close down visual studio to free up the locks on these files.
Hope this helps!
-Jeff
