When you run MSVSMON.EXE on Vista, do you get the dreaded message indicating that you need to set the firewall, but when you do, MSVSMON.EXE errors out with an Incorrect Function message? After much struggle, I finally found the trick to remote debugging working correctly. Many thanks to this post on the MSDN Forums from Sam George.
It seems that even with the Vista SP1 Update, MSVSMON.EXE does not properly set the firewall. You’ll need to set it up manually with the following batch file:
netsh advfirewall firewall add rule name=”Microsoft Visual Studio Remote Debugger – UDP 137″ dir=in action=allow enable=yes localport=137 protocol=udp
netsh advfirewall firewall add rule name=”Microsoft Visual Studio Remote Debugger – UDP 138″ dir=in action=allow enable=yes localport=138 protocol=udp
netsh advfirewall firewall add rule name=”Microsoft Visual Studio Remote Debugger – TCP 139″ dir=in action=allow enable=yes localport=139 protocol=tcp
netsh advfirewall firewall add rule name=”Microsoft Visual Studio Remote Debugger – TCP 445″ dir=in action=allow enable=yes localport=445 protocol=tcp
Of course, make sure you run the batch file from an elevated command prompt.
Microsoft Azure and Amazon Web Services (AWS) are two of the most popular cloud platforms.…
Cloud management is difficult to do manually, especially if you work with multiple cloud…
Azure’s scalable infrastructure is often cited as one of the primary reasons why it's the…
https://www.youtube.com/watch?v=wDzCN0d8SeA Watch our "Unlocking the Power of AI in your Software Development Life Cycle (SDLC)"…
FinOps is a strategic approach to managing cloud costs. It combines financial management best practices…
Using Kubernetes with Azure combines the power of Kubernetes container orchestration and the cloud capabilities…