Debbuging locally by attaching to process - is this supposed to work?

Sep 10, 2014 at 6:01 PM
.. because so far I couldn't make it work by attaching to node.exe process...
Coordinator
Sep 10, 2014 at 6:51 PM
Going through Debug -> Attach to Process and attaching to node.exe will not work (you'll end up debugging Node.js in native mode instead). However, you can attach by following the instructions here under the section "Attaching the NTVS debugger", so long as you've launched your node.exe process with --debug.
Sep 10, 2014 at 7:45 PM
I tried that too, let me make sure I understand:

node --debug server.js
"... debugger listening on port 5858.."

Then I should put "localhost:5858" as qualifier in Attach to Process, screen, correct? If I do this and I hit Refresh, I get "Unable to connect to the Microsoft Studio Remote Debugging Monitor named 'localhost:5858'"..
Coordinator
Sep 10, 2014 at 8:26 PM
It sounds like you didn't set the transport to Node.js Remote Debugging.
Marked as answer by StanB on 9/11/2014 at 2:55 PM
Sep 11, 2014 at 11:44 AM
Transport: Node.js remote debugging
Qualifier: tcp://localhost:5858
Error: Could not attach to Node.js process at tcp://localhost:5858/: .. The requested name is valid, but no data of the requested type was found
Coordinator
Sep 11, 2014 at 8:05 PM
This is really weird. This error message is coming from .NET, and it happens when it can't DNS-resolve the hostname - but being unable to resolve "localhost" would indicate that something is really broken in the machine configuration.

Anyway, can you see if using 127.0.0.1 instead gets you past that?
Marked as answer by StanB on 9/11/2014 at 2:55 PM
Sep 11, 2014 at 9:54 PM
tcp://127.0.0.1:5858/ worked... thanks!