Suppose to have a problem in your program occurring only a specific PC.
You can study it by:
- installing a copy of your VS2017 on that PC.
- copy VS2017 Remote Debugger console
Naturally the second way is simpler and more efficient, since you have to copy a folder.
You can find it, in the following path:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Remote Debugger
or (into 32 bits Windows PCs):
C:\Program Files\Microsoft Visual Studio\2017\Professional\Common7\IDE\Remote Debugger
It contains both 32 and 64 bits version and proper version according to your project type (32 on 32 bits projects, 64 on 64 bits ones).
To start a remote debug session you need:
- network connection to the target PC.
- copy the proper VS2017 remote debugger client into the target machine.
- copy a debug version of your project for the target PC.
- start remote debugging client (I suggest with administrative rights).
then you can connect your VS2017 to:
and start debugging the program, or attach to its process, and start the session.