Oct 21, 2014 at 6:20 PM
Edited Oct 21, 2014 at 6:53 PM
(I'll try to cut to the chase)
Node Tools for Visual Studio installed.
Express server invoking CLR library
I need to automate a way to debug the library directly with a stripped version of the Express server.
So, the way I approached this was to modify the MSBuild of the library's project file to add
The node executable is bundled with the development repository and server.js is co-located with it. If I remove the StartArguments, a node instance spins up and waits; however, the introduction of the server config file as a StartArgument results in
'The program ' node.exe' has exited with code 8 (0x8)'
Note that I changed the StartArguments to a known to be invalid value ("foo") and the same error was generated, so it seems the error I'm getting is either a very generic one or the debugger cannot locate my server.js file.
So this is why I posted the question: having to think about communicating my approach in a way that others can consume has led me
a solution. The StartArguments are obviously wrong. Changing it to be
<StartArguments>$(SolutionDir)Edge.Express\server</StartArguments> caused the debugger to at least attempt to load up symbols. The server instance that it spins up in the external console still crashes, and it seems to be reporting an error, but
when it crashes, Visual Studio kills the process and I cannot get the error out of the spawned process in order to inspect.