- Visual studio 2017 remote debugger rpi how to#
- Visual studio 2017 remote debugger rpi windows 7#
- Visual studio 2017 remote debugger rpi windows#
The path you need to use may be different.
The following example opens port 4026 for the remote debugger on the remote computer.
Visual studio 2017 remote debugger rpi windows#
The new rule should appear and be selected in the Inbound Rules or Outbound Rules list.įor Windows Firewall, you can use PowerShell commands such as New-NetFirewallRule. Select one or more network types to enable, including the network type for the remote connection, and then select Next.Īdd a name for the rule (for example, msvsmon, IIS, or Web Deploy), and then select Finish. Select Allow the Connection, and then select Next. Under Specific local ports, enter a port number from the following tables, and select Next. Select either TCP or UDP, depending on the port number from the following tables. In the New Inbound Rule Wizard, select Port, and then select Next. For an outgoing rule, select Outbound Rules instead. In Windows 10, this is Windows Defender Firewall with Advanced Security.įor a new incoming port, select Inbound Rules and then select New Rule. In Windows Start menu, search for and open Windows Firewall with Advanced Security. However, in some scenarios, such as a third-party firewall, you may need to open ports manually. Visual Studio and the remote debugger try to open the correct ports during installation or startup.
Visual studio 2017 remote debugger rpi windows 7#
Windows 8/8.1, Windows 10, and Windows Server 2012 settings use the word app, while Windows 7 and Windows Server 2008 use the word program.
The instructions for configuring the Windows firewall differ slightly on different operating systems, and for older versions of Windows. For example, the Visual Studio computer can run Windows 10, and the remote computer can run Windows Server 2012 R2. The Visual Studio and remote computer don't have to be running the same operating system.
Visual studio 2017 remote debugger rpi how to#
This topic describes how to configure the Windows firewall to enable remote debugging on Windows 10, 8/8.1, and 7 and Windows Server 2012 R2, 2012, and 2008 R2 computers. Visual Studio and the remote debugging tools try to open the correct firewall ports during installation or startup, but you may also need to open ports or allow apps manually. On a network protected by Windows Firewall, the firewall must be configured to permit remote debugging. Apparently, telling >node<< to wait means that the RemoteDebug script doesn't get to start up.Configure Windows Firewall for remote debugging I discovered that the RemoteDebug.js script supplied by Microsoft accepts a command line argument to wait for the remote debugger to attach. How do I open the port on the Pi side? I thought that the message the debugger is listening on 5858 meant the port was "open", but that's clearly not the case. I've confirmed that Visual Studio 2017 is allowed to access private networks through the Windows firewall. No connection could be made because the target machine actively refused it 10.0.0.78:5858 When I try to attach to the remote process from within Visual Studio I get the following error:Ĭould not attach to Node.js process at tcp://majordomo:5858/: I'm using the -debug-brk switch because the bug I'm trying to find throws an exception during the app's startup, so I need nodejs to wait until a debugger is attached.
$ nodejs -debug-brk RemoteDebug.js app.js
0 kommentar(er)
