Visual Studio 2008 Remote Debugging

 Remote Debugging Monitor (msvsmon.exe) is a small application, Visual Studio connects to for remote debugging.
VS supports remote debugging, so that your company can remotely debug the program on the client of the < br> VS remote debugger is divided into two:
Direct Remote Debugging: The testing method must be in a VS project file can only be used under (because the address of machine to be debugged in the project file), the specific content, please See: in the way the process of commissioning a
Additional: Please see the specific content: the method in the second
here I am only a few notable places to
1, an additional process of debugging is divided into two types: (1) Window authentication, remote debugging (2) anonymous remote debugging
Windows as the host on remote debugging in the debug process to use VS add-in default mode, where the remote mode, please be careful not to be deceived literally means, Remote (no authentication is limited to the machine) the same Windows user account name and password to do so is to verify the identity of debugging machine.
remote debugging to debug local services as may be exempted from user name and password Windows account
directly supports only Visual Studio Remote Debugging Remote Debugger windows authentication on the debug mode, do not support remote debugging to debug machine as a service and remote debugging
anonymous anonymous remote debugging there is a problem, additional process on The process is not being debugged machine user name, leading to a breakpoint set on the whole VS does not work, feel like a dummy ..... anonymous remote debugging has yet to find a solution ........< br> anonymous Remote debugging time if there is no choice in the msvsmon remote debugging in the anonymous use the same user name and password you will still find that additional processes appear to be the process of debugging machine or not the user name, which is still set breakpoints does not work that
2, set the preconditions
:
debug machine and the machine being debugged in a local area network, and must be on a network segment
debugging debug machines and machines must be logged in to be the same user, the user name must have been
off the firewall or open the appropriate port, usually 4015
machine being debugged debugging machine and local network access security policy must be changed to ; Local Security Settings -> Local Policies -> Security Options -> Network Access
debugging method:
this point there are two kinds of debugging method: one is the anonymous testing, no verification, one is the identity Window Verify debug:
Anonymous debug:
1. msvsmon machine being debugged, select Tools -> Options, click No Authentication mode (only local)
2. then you can see the host name and IP, is generally hostname: 4015 in the form of
3. debug machine open VS, select the Attach to Process
4. transport select remote (no authentication is limited to the machine)
5. qualifiers select hostname : 4015, after which the process of refreshing to see a list of the
Window authentication debug: This method requires debug to debug machine machine and the user name and password exactly the same
1. msvsmon machine being debugged, select Tools - > Options, click on the windows authentication
2. debug machine open VS, select the Attach to Process
3. Transport Select the default
4. qualifiers select username @: hostname, then refresh you can see Remote debugging process list of the

a C # WinForm program, computer configuration
0. System Requirements
local: the local computer that contains all the source code, of course, ha ha VS installed on the ah
remote: As shown in
1.
steps select Tools | Permission | In the Group or user names need to add the name of the remote computer
Note: local and remote computers must use the two the same account to log
select Tools | Option |, be sure to select test
II
Method One solution:
1. Open the project's property pages;
2. navigate to the Debug tab,
Start Action: Select ; to 172.25.145.51 debug Walkthrough_SimpleDebug.exe
(fill in the address here is the meaning: the remote computer exe file, this directory need to fully share)
Start Options: Working Directory choice 172.25. 145.51 debug
Use remote machine: 172.25.145.51
At this point, F5 can debug the remote application of the
Method Two: Binding process method
open VS2008, select the Debug --- Attach to Process
III
local test environment: WinXP SP2 + VS2008 ENU
remote Win2003