Menu
I'm doing remote debugging regularly thanks to Visual Studio 2010's msvsmon tool. I used to set the timeout to zero in the options screen, as I just want the tool to keep running until I'm done with it:
This works fine, but I grew tired of doing this everyday and I'm trying to do it from a script, using the appropriate command line switch:
msvsmon.exe /timeout:0
But no cigar:
I can work around this by setting a ridiculously long timeout, but I'm just checking: is there a proper way to disable this timeout from the command line? Or maybe with a registry key?
347
You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select Debug > Attach to Process or press Ctrl+Alt+p in Visual Studio, and use the Attach to Process dialog to attach the debugger to the process.
05 On the General settings panel, under Debugging, select Off next to Remote debugging setting to disable remote debugging using Microsoft Visual Studio for the selected Azure App Services web application.
Select Configure remote debugging to configure the firewall and start the remote debugger. When configuration is complete, the Remote Debugger window appears. The remote debugger is now waiting for a connection. Use the server name and port number shown to set the remote connection configuration in Visual Studio.
Well if there's no proper way, I guess the best is just to use the maximum allowed, which seems to be the maximum of a signed integer, minus one:
msvsmon.exe /timeout:2147483646
That leaves more than 68 years of remote debugging, should be enough for me!
173
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With