I'm working on an app here at the office which is currently made up of one executable and one DLL full of objects shared by (currently) 2 programs. I'm working in both of these projects simultaneously so I've got two copies of VS2005 open on my machine. Dual monitors makes this a pleasure to work with. However, something odd happens every once in a while. If I make a change in the DLL and build the change, some times (and not every time or even every other time) the EXE will "lose" the DLL and all my namespace objects will suddenly be reported as invalid. The only solution which reliably works is to close VS2005 and re-open it. Possibly simply closing and opening the solution would work but by this time I'm generally pissed that my work's been interrupted so killing the entire thing is more satisfying.
Anyone else having this kind of problem?
No, I can't simply put the two projects into the same solution and use one instance of VS2005 because my co-developer likes to interface to VSS via Visual Studio. This means less control about how source code is stored in VSS (I like the VSS client interface myself). If both projects were in the same solution, VS2005 would want to store the files in the same branch of VSS and that's not how we have our shared DLL stored.
-- Matt Ranlett