Remote Debugging Components
This topic applies to:
Visual Studio Edition |
Visual Basic |
C# |
C++ |
J# |
Visual Web Developer |
Express |
No |
No |
No |
No |
No |
Standard |
No |
No |
No |
No |
No |
Pro/Team |
Yes |
Yes |
Yes |
Yes |
Yes |
The following tables show the files needed for remote debugging. The easiest way to install these files is by running Remote Components Setup.
Native Debugging
File | Install Location |
---|---|
msvsmon.exe |
Anywhere on remote machine There are separate versions of msvsmon for 32-bit and 64-bit debugging. Make sure you install the proper version on the remote machine. |
dbghelp.dll |
In the same directory as msvsmon. This optional file is used for saving dumps of an application. If this file is not installed, the debugger saves dumps using the default version dbghelp.dll installed with the operating system. |
msdbgui.dll |
In the same directory as msvsmon. This optional file contains localized strings, dialogs and help for the remote debugger. If this file is missing, the debugger uses default English resources. |
Managed Debugging
File | Install Location |
---|---|
msvsmon.exe |
Anywhere on remote machine. |
msvsmon.exe.config |
In the same directory as msvsmon. Required to load the correct .NET Framework version. |
Symsrv.dll |
In the same directory as msvsmon. Required if you use symbol server with remote debugging. |
mcee.dll |
In the same directory as msvsmon. Required to debug C++ code that uses the .NET framework. |
msvb7.dll, msvb7ui.dll |
In the same directory as msvsmon. Required for Visual Basic debugging only. |
vjscompee.dll, vjscompeeui.dll |
In the same directory as msvsmon. Required for Visual J# debugging only. |
Special Components
File | Purpose |
---|---|
AvVsPkDH.dll |
For running an applications under Application Verifier. See your Application Verifier documentation for setup. |
mpishim.exe |
For debugging an application on a cluster. See How to: Debug a Remote Cluster Application. |
Stepping Into Web Services Calls
T-SQL debugging and stepping into Web service calls require additional components, which must be installed into specific locations and registered in the Registry. Manual installation of these components is not recommended. Use the Visual Studio Setup program to install and register these components. For more information, see Setting Up Remote Debugging.