This project is read-only.

VS 2013 (update 4) crashing when trying to open node project in it

Jan 14, 2015 at 9:44 PM
My Visual Studio just opens the project created using node and then hangs and after a few minutes it just creates. I tried installing and uninstalling this tool multiple times but nothing worked.
(I was following this link of John Papa's blog -

I have following:
Visual Studio 2013 Update 4 with Code Rush
Nodejs version 0.10.35. Is this a known issue?
Jan 14, 2015 at 9:54 PM
Hi ameghwal - would you mind clarifying something for me? Have you installed Node.js Tools for Visual Studio (NTVS) and are you using the "create from existing" template, or are you using File > Open Web Site as specified in the blog?

If you do have NTVS installed, which version?
Jan 14, 2015 at 9:55 PM
Edited Jan 14, 2015 at 9:56 PM
I am using File > Open Web Site as on the blog. I have NTVS installed. (previously I was not having that, but it is crashing in both the cases)

Jan 14, 2015 at 10:20 PM
Edited Jan 14, 2015 at 10:21 PM
Okay - I know it's kind of confusing, but unfortunately our team (Node.js Tools for Visual Studio) does not own that part of the VS experience, and can't help much there. That said, we're happy to forward this discussion thread onto them, and you can also consider filing a bug on them according to the steps here:

However, one way you should be able to workaround the issue is by downloading our Node.js Tools extension available on this site, which is specifically targeted towards managing Node.js projects and gives you a whole bunch of helpful tools to work with (whereas File > Open Web Site is generic for all websites). Once you have it installed, you can follow the steps for importing an existing project here:

A couple other notes if you decide to use NTVS:
  • NTVS's debugging won't work unless you're using Node.js version 0.10.33 as specified on the download page due to a bug in Node.js that's expected to be fixed in 0.10.36:
  • We've had performance bugs related to ReSharper, but not CodeRush - so hopefully it works out fine, but if you are experiencing memory/performance issues, that would be the first thing to try disabling
And the plus side of using NTVS is that if you ever experience any issues, it will be easier for us to debug and fix them :-)
Jan 15, 2015 at 1:44 PM
Thanks a lot. I'll use the importing steps link.