Shulou(Shulou.com)06/02 Report--

Today, I will talk to you about how to carry out Visual Studio 2012 Universe 2010 Universe 2008 remote debugging. Maybe many people don't know much about it. In order to make you understand better, the editor summarizes the following contents for you. I hope you can get something according to this article.

Deployment environment: ASP.NET (C #) + IIS+Win7 64 bit

At this point, the developer will have several ideas:

1. Deploy the server environment locally, and then throw the generated dll into it for debugging. At this point, there will be several results, if it goes well, through debugging to solve the bug, if not, it will extend the resolution time of bug. Unsmooth situations may be: not familiar with the configuration of the program, the local may lack of registration for that plug-in in the registry, the directory may exist in Chinese. All kinds of problems.

2, install a Visual Studio 2008 / 2010 / 2012 on the server [hereinafter referred to as the vs tool], then copy the program file to it, then attach the generated file dll to the iis process for debugging, , successfully solved the bug, but half a day passed by looking at the clock. And the server has a lot of files, just for you to debug the program's files. It makes sense if it is a company whose management is not very strict, otherwise it will be sprayed.

All right, stop talking and get to the point.

Remote debugging method

* step: copy the Remote Debugger folder in the vs tool to the target machine. The approximate directory should be: d:\ Program Files (x86)\ Microsoft Visual Studio 10.0\ Common7\ IDE\ Remote Debugger, or you can find its shortcut from the start menu, as shown below:

Step 2: open the Remote Debugger folder on the server. If it is 32-bit, run msvsmon.exe in X86. If it is 64-bit, run msvsmon.exe in X64. Note here about 32-bit and 64-bit, mainly your IIS application pool, right-click on the application pool, click Advanced Settings, the following form will appear. If the 32-bit application is enabled and set to true, then you need to run msvsmon.exe in X86.

After running, the following interface appears

Step 3 [the most critical step]: set your local account password to be the same as the server, because remote debugging also requires user credentials. The account number and password should be the same!

Step 4: open your program source code with the vs tool, and use the shortcut key ctrl + alt + p to open the additional process form, as shown in the following figure

Transport: default

Qualifier: default is the local machine name, set to your server IP (for example: 192.168.1.250)

Set up and press enter to see the progress of the machine, then find the w3wp.exe process, and click attach. [if you don't see w3wp.exe, you can check the processes shown below for all users]

Then enjoy the debugging of the code.

About debugging that technology.

Compare the following two debugging methods to see who has committed the crime, but I have. ^ _ ^

1, in order to debug a dll and directly press F5 in the Web program to debug, if it is a small project small website, that is no problem. If it is a website of tens or even hundreds of megabytes, then the problem comes. This kind of debugging is very slow, and every time you need to regenerate the dll of the entire site, the speed is unbearable.

2. Regenerate the dll you need to debug, copy the dll and pdb files to the released website bin directory, then ctrl + alt + p attach to the IIS process w3wp.exe, and then you can debug your dll. This is fast and convenient, so be a happy programmer.

After reading the above, do you have any further understanding of how to carry out remote debugging of Visual Studio 2012 Universe 2010 Universe 2008? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.