sclubolz.blogg.se - Visual studio remote debugging port number

After a while, the software interface appeared on the screen of the remote computer.

After the copy is completed, a prompt box will pop up, asking you to enter the username and password of the remote computer for verification

Click VS Run, you can see that new files are generated in the remote directory of the remote computer.

Xcopy $(SolutionDir)\Bin\Debug \\.XX\xxx\Bin\Debug\ /E /Q /Y Stupid method: after successful compilation-copy-paste to the remote computerĬool method: In the VS generation event, set the post-generation event command line (as shown below) Please replace the XXX here with the directory corresponding to the IP and project by yourself Right-click this shared Debug folder and select properties, and set the share to EveryOne.Ĭopy the latest compiled Debug folder of this machine to the Debug directory of the remote machine The picture above is the debugging machine ③Configuration of remote debugging directoryĬreate a new Debug directory in the remote computer, and require the Debug path in the machine where VS is installed Exactly the same Open the project properties of Visual Studio, check Use remote computer in the debugging column, and enter the remote computer name and port number shown in the figure above.Run msvsmon.exe to configure secure login connection information Right-click Visual Studio->Open the file location->Find the Remote Debugger folder in the current directory->Copy and paste to your remote computer, and run the program msvsmon.exe of the desired platform in the remote computer Second, the text ① Install Remote Debugger This article mainly describes Remote debugging of WPF, WinForm applications

The principle is to copy compiled files to a remote computer and connect to VS through the network. , Without the need to install the VS environment on the test machine.Ĭompared with UWP, ASP and other projects, the remote debugging of traditional desktop client is more troublesome to configure, because it is a non-deployed application. The solution is to use the remote debugging function of Visual Studio, you can directly use the test machine as the debugging target, and directly track breakpoints and exceptions, and you can quickly find the wrong place like debugging on the local machine. In the development process, you may need to use Win7, Win8, Win10 and other different versions of the system to do compatibility debugging, and sometimes to optimize for special graphics cards, wireless network cards and other hardware devices.