First, let's talk about the operating environment. The project asp.net MVC version is 4.5, and the remote server is Windows Server 2016 x64-bit system, and the native win10 x64-bit system is the system.
VS installation directory to find the Remote Debugger directory, there will be 3 versions "Appx", "x64", "x86" under the directory, since our server is an x64-bit version, so copy the x64 folder directly to our remote server.
Remote Debugger directory
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Remote Debugger
The many wrong directories on the Internet are: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
We open the folder we just copied on the remote server, find the "msvsmon.exe" program and run it as an administrator, and set it in the tool options as follows:
(No authentication, allow any user to debug, ports can be set by themselves or leave the default)
We publish the project to the server, and when we publish,Note that the configuration is selected as the "Debug" optionAs follows:
Package the generated release package and upload it to the server for publishing, there are steps, so I won't talk about it here.
The code that needs to be debugged for the controller is as follows:
Let's request it directly, and it returns normal, as follows:
Remote commissioning
In VS, select Debug - Attach to Process, select "Remote (Unauthenticated)" for the connection type, enter ip:port for the connection and destination, and enter! As shown below:
Select the process that needs to be debugged below, the process named "w3wp.exe", and attach it! Re-requesting the URL, we can find the power failure that successfully entered the settings, as shown in the figure below:
Finally, attach links to various MS remote debugging help documents:The hyperlink login is visible.
|
Posted on 5/23/2018 5:27:57 PM
|
|
|
|
