Compartir a través de

Preparing a Test Machine To Run a Debug Executable

  • Artículo

 

The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.

The latest version of this topic can be found at Preparing a Test Machine To Run a Debug Executable.

To prepare a computer to test the debug version of an application that is built with Visual C++, you have to deploy debug versions of the Visual C++ library DLLs that the application depends on. To identify which DLLs have to be deployed, follow the steps in Understanding the Dependencies of a Visual C++ Application. Typically, debug versions of Visual C++ library DLLs have names that end in "d"; for example, the debug version of msvcr100.dll is named msvcr100d.dll.

Note

Debug versions of an application are not redistributable, and debug versions of the Visual C++ library DLLs are not redistributable. You may deploy debug versions of applications and Visual C++ DLLs only to your other computers, for the sole purpose of debugging and testing the applications on a computer that does not have Visual Studio installed. For more information, see Redistributing Visual C++ Files.

There are three ways to deploy debug versions of Visual C++ library DLLs together with the debug version of an application.

  • Use central deployment to install a debug version of a particular Visual C++ DLL to the %windir%\system32\ directory by using a Setup project that includes merge modules for the right library version and architecture of your application. Merge modules are found in the Program Files or Program Files (x86) directory in \Common Files\Merge Modules\. The debug version of a merge module has Debug in the namefor example, Microsoft_VC110_DebugCRT_x86.msm. An example of this deployment may be found in Walkthrough: Deploying a Visual C++ Application By Using a Setup Project.

  • Use local deployment to install a debug version of a particular Visual C++ DLL in the application’s installation directory by using files that are provided in the Program Files or Program Files (x86) directory in \Microsoft Visual Studio <version>\VC\redist\Debug_NonRedist\.

    Note

    For remote debugging of your application built by using Visual C++ 2005 or Visual C++ 2008 on another computer, you have to deploy debug versions of Visual C++ library DLLs as shared side-by-side assemblies. You can use either a Setup project or Windows Installer to install corresponding merge modules.

  • Use the_Deploy option in the Configuration Manager dialog box in Visual Studio to copy the project output and other files to the remote computer. An example of this deployment may be found in Set Up Remote Debugging for a Visual Studio Project.

After Visual C++ DLLs are installed, you can run a remote debugger on a network share. For more information about remote debugging, see Set Up the Remote Tools on the Device.

See Also

Set Up the Remote Tools on the Device
Deployment in Visual C++
Windows Installer Command line options
Deployment Examples