How to enable script debugging in Visual Studio from Internet Explorer

Nov 22, 2013 at 12:33 PM
With the ASP.NET templates we had the oppurtinity to debug javascript files from the internet explorer in visual studio. This doesn't seem to work with the new Nodejs template (only nodejs files works).

We set up the configuration from the following tutorial:
http://msdn.microsoft.com/en-us/library/vstudio/z959x58c.aspx

Have we missed something or is this currently not available?
Coordinator
Nov 25, 2013 at 6:41 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Coordinator
Nov 25, 2013 at 6:44 PM
It's currently not available, we concentrated on the core node.js debugging for alpha. Please vote for the feature (the work item linked above) if it's important to you, we look at the number of votes when prioritizing work.
Coordinator
Nov 25, 2013 at 8:32 PM
Note that this is, technically, a regression - client-side IE debugging is already available in VS, so it should just work everywhere. The reason why it doesn't is probably because we hijack all .js files in the project for our own debugger. We should provide some way to specify that a given .js file is a client file (probably via the Properties window), and hand it off to the regular JS debugging engine if that's the case.
Nov 25, 2013 at 9:43 PM
Edited Nov 25, 2013 at 9:45 PM
Specify the .js files as client files would be definitely a relief. Maybe on a folder too?

/ (nodejs files)
/public/app (client javascript files)
Coordinator
Nov 26, 2013 at 12:51 AM
I actually wonder if there may be a way to work around it. Try opening the .js file from Solution Explorer via right-click -> Open With, and select "Source Code (Text) Editor". Then try setting breakpoints in that.
Nov 26, 2013 at 12:32 PM
Edited Nov 26, 2013 at 12:35 PM
Doesn't seem to work with the "Open With" way.

Actually you can create a empty Web application and install ["iisnode for iis 7 express"] (https://github.com/tjanczuk/iisnode) (works with newer versions (8.x) too) and a "From Existing Node.js code" project.

Its really hacky and you need to switch between the two projects, but still better then work with node inspector or something else.