When I upgraded some really obvious windows symbols was missing. After further investigation i found that a cmd.exe had the database files locked so no database could be built.
Not that I have noticed, but I have tried a few versions without rebooting the machine. VAssist deosn't warn about this so it might have happened a couple of versions ago.
The installer might invoke DllRegisterServer on VA in a console session - not sure of the install process. But DllRegisterServer (called during install) does clean all the symbol databases. The installer isn't supposed to run if any IDE instances are running - any chance an instance was started after install started but before it finished?
(Install/uninstall of VA does not require a reboot.)
The installer told you it had to reboot? I've never seen it happen. Maybe there was a problem removing a file - and needed to reboot to delete at startup?
Visual Studio 2005 RC. I noticed this directly after installing 1423. I'm pretty sure I didn't start Visual Studio until the installer was fully finished.
It was the cmd process holding the files locked acording to process explorer not regsvr32.exe
Uniwares i have seen previous installers tell me to reboot, but not for several builds now. for me this seems to be triggered by one of the Microsoft Office 2000 programs being open. i think something they are doing with macros is involved in this.
i have just installed both VS 2005 RC and VA 1423 on a clean win2k machine. after the install everything seems to be working just fine. certainly VA is parsing and understanding the C++ code that i have loaded and am editing.
were there any running programs that could have been factors?
I see no reason for another program (especially an hidden cmd.exe process) to lock the files in the Visual Assist vc8 directory. I have no antivirus, or other system wide software running. This is probably one of those unreproducible bugs that only happen once.
I think I might have run devenv.exe from the command line to do automated builds this reboot (not while installing VAssist), but I'm not sure.
Uniwares i have seen previous installers tell me to reboot, but not for several builds now. for me this seems to be triggered by one of the Microsoft Office 2000 programs being open. i think something they are doing with macros is involved in this.
Definitely no Office app around at the time of installation. No Macro IDE either. Firefox, Explorer (without all the office add-ins), thats it. But as I said its been a long time since I saw that last time.
Topic Locked
Posted - Sep 22 2005 : 08:28:37 AM
