S
Sam Vanhoutte
Hello,
I am using Visual Studio 2003 with the framework 1.1. Yesterday I installed
the new professional version of Office 2003 (dutch version). I overwrote
the old (XP) version and changed the default (install on first use) settings
to install directly on disk for the .NET support in all the Office
Applications.
After this install, I was unable to debug my VB.NET projects. I got this
error message:
--
Error while trying to run project: Unable to start debugging.
The debugger is not properly installed. Run setup to install or repair the
debugger.
--
I just managed to solve this problem. It appears that the Office 2003
installation has overwritten a file in the Common Files directory that is
used by the Visual Studio Debugger.
I followed the routine that was described in this google.thread
(http://groups.google.be/groups?q="error+while+trying+to+run+project"+md
m.exe&hl=nl&lr=&ie=UTF-8&oe=UTF-8&selm=OrR6H3scDHA.460%40cpmsftngxa06.phx.gb
l&rnum=1)
<quoting Bradley Jiang[MSFT]>
1. Replace the following files with their equivalents from the Visual
Studio .NET
installation media:
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
2. Register each DLL above with regsvr32.EXE, e.g:
regsvr32 "ProgramFiles\Common Files\Microsoft Shared\VS7Debug\coloader.dll"
3. Re-register each executable, e.g:
"Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit" /regserver
"Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe" /regserver
</end quoting>
It appears that the file MDM.EXE caused the problem, as it was modified
during the Office setup. I guess this is some kind of a bug? And will the
..NET integration work in my Office applications?
kind regards...
Sam Vanhoutte
I am using Visual Studio 2003 with the framework 1.1. Yesterday I installed
the new professional version of Office 2003 (dutch version). I overwrote
the old (XP) version and changed the default (install on first use) settings
to install directly on disk for the .NET support in all the Office
Applications.
After this install, I was unable to debug my VB.NET projects. I got this
error message:
--
Error while trying to run project: Unable to start debugging.
The debugger is not properly installed. Run setup to install or repair the
debugger.
--
I just managed to solve this problem. It appears that the Office 2003
installation has overwritten a file in the Common Files directory that is
used by the Visual Studio Debugger.
I followed the routine that was described in this google.thread
(http://groups.google.be/groups?q="error+while+trying+to+run+project"+md
m.exe&hl=nl&lr=&ie=UTF-8&oe=UTF-8&selm=OrR6H3scDHA.460%40cpmsftngxa06.phx.gb
l&rnum=1)
<quoting Bradley Jiang[MSFT]>
1. Replace the following files with their equivalents from the Visual
Studio .NET
installation media:
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
2. Register each DLL above with regsvr32.EXE, e.g:
regsvr32 "ProgramFiles\Common Files\Microsoft Shared\VS7Debug\coloader.dll"
3. Re-register each executable, e.g:
"Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit" /regserver
"Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe" /regserver
</end quoting>
It appears that the file MDM.EXE caused the problem, as it was modified
during the Office setup. I guess this is some kind of a bug? And will the
..NET integration work in my Office applications?
kind regards...
Sam Vanhoutte