Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following instructions are describing the configuration steps, regarding the Remote Debugging with VS17 on an Azure VM.
Download Visual Studio Remote Tools
Preliminary, we must check the VS version. Each version corresponds to different Remote Tools
Visual Studio Version | Link |
2017 | download |
2015 Upd 3 | download |
2013 | download |
Install Remote Tools
At the first step, check Accept the license terms and conditions and click Install.
http://cloudopszone.com/wp-content/uploads/2018/04/RT.jpg
setup is running...
http://cloudopszone.com/wp-content/uploads/2018/04/rt2.jpg
And finally, the setup is successful
http://cloudopszone.com/wp-content/uploads/2018/04/rt3.jpg
Remote Tools Configuration
Open the Remote Debugger icon
http://cloudopszone.com/wp-content/uploads/2018/04/desktop-shortcut-RT.png
Tools - Options, check No Authentication / Allow any user to debug and click OK
http://cloudopszone.com/wp-content/uploads/2018/04/RT-Configuration.jpg
After having downloaded and installed the correct VS version we need to configure both Windows & Azure Firewalls.
Visual Studio Version | Port |
2017 | 4022 |
2015 | 4020 |
2013 | 4018 |
Windows Firewall Configuration
PURPOSE | TCP PORT | NOTES |
Remote Tools | 4022 | Default TCP Port for Visual Studio 2017 Remote Debugger |
Azure Firewall Configuration
http://cloudopszone.com/wp-content/uploads/2018/04/AzureFirewalll.jpg
*** If a Load Balancer exists then we must add the following Inbound Rule *** |
Azure Load Balancer NAT Rule
http://cloudopszone.com/wp-content/uploads/2018/04/LBNatRule-1.jpg
......One step away debugging
Open Visual Studio, Debug-Attach to Process...
http://cloudopszone.com/wp-content/uploads/2018/04/vs_attach.png
Type on Connection Target field, IP address:Port, e.g XXX.XXX.XXX.XXX:4022, and Click Refresh.
http://cloudopszone.com/wp-content/uploads/2018/04/AttachToProcess.png
Possible Error Messages
Remote debugger does not appear to be running
http://cloudopszone.com/wp-content/uploads/2018/04/error_msg_01.png
Causes
- Possible firewall (Windows or Azure), Azure Load Balancer (if exists) misconfiguration.
- Remote Tools process is not running
Connection Request was rejected
http://cloudopszone.com/wp-content/uploads/2018/04/error_msg_02.png
Causes:
1. On the Remote Debugger, check if the Options are not configured correctly.