Problems encountered in remote debugging of Visual Studio 2012

Sometimes the development environment does not have the problem of code in the production environment will be some development environment can not reproduce the problem, or need to remote debugging production environment code to do?

VS has been provided to developers for remote debugging tools

The following is a brief talk about how to use,
Pre-Preparation:
1, the local login account, the password with the remote server consistent (VS2012 previously needed, now I did not test, just do the same, province to get the problem)
2, according to the server system version copy the corresponding remote debugging tools to the server
Then run the msvsmon.exe inside.


3, local open vs, tools-"additional process


Note: qualifier here to fill in the computer name, can not fill the IP, I fill in the IP direct error
The local code is consistent with the server code and the PDB file must be copied
Of course, before adding the computer name in the C:\windows\system32\drivers\etc\ below the hosts file to do the local resolution of the server computer name!
If you are monitoring the IIS process, do not see the corresponding site process, you can access the remote site locally, and then refresh you will see

After attaching a process, direct local interrupt point debugging, remote debugging will be a bit slow

Problems encountered in remote debugging of Visual Studio 2012