Yesterday, Office 2007 had caused an error itself and decided to repair itself, then some installation screens popped up.. a total mess that led my Visual Studio 2003 environment to stop debugging.
After a search on the internet I found that, this inproper setup attempt could affect the following files:
Program Files\Common Files\Microsoft Shared\VS7Debug\coloader.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\csm.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\pdm.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe
Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe
I replaced the files from a proper machine and registered them again by typing the following lines to the command window.
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG\coloader.dll"
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG\csm.dll"
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG\msdbg2.dll"
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG\pdm.dll "
"c:\Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit" /regserver
"c:\Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe" /regserver
Details of the error:
-The debugger was not working properly but the exe file could run without debugging
Enjoy Coding!