Currently, debugging Node remotely requires the exe to be started on the target device and then from VS you use Attach to Process.
It would be great if I could create a Node project and have the ability to:
1. Deploy Node and project JS files to target device.
2. Start Node on target machine and attach debugger automatically.
Basically have behavior that is similar to debugging locally with just pressing "Start"
Comments: This needs to be more specific, since deployment methods can vary a lot depending on what the device supports. Today, we support deployment to Azure web sites and cloud services. Web sites in particular use the standard VS publish functionality that is also used for web projects in other languages, and that has a number of publish targets - Web Deploy, obviously, but also FTP or generic filesystem copy. I'm not sure if that is extensible on UI level, but the publish pipeline on MSBuild level definitely is (it's just a target, and it builds up a list of files before handing it over). Similarly, for starting node on the target device, that device needs to expose some protocol that enables such a thing, and reports completion so that VS knows to attach.
It would be great if I could create a Node project and have the ability to:
1. Deploy Node and project JS files to target device.
2. Start Node on target machine and attach debugger automatically.
Basically have behavior that is similar to debugging locally with just pressing "Start"
Comments: This needs to be more specific, since deployment methods can vary a lot depending on what the device supports. Today, we support deployment to Azure web sites and cloud services. Web sites in particular use the standard VS publish functionality that is also used for web projects in other languages, and that has a number of publish targets - Web Deploy, obviously, but also FTP or generic filesystem copy. I'm not sure if that is extensible on UI level, but the publish pipeline on MSBuild level definitely is (it's just a target, and it builds up a list of files before handing it over). Similarly, for starting node on the target device, that device needs to expose some protocol that enables such a thing, and reports completion so that VS knows to attach.