This project is read-only.

1.0 Beta

Rating:        Based on 28 ratings
Reviewed:  24 reviews
Downloads: 23562
Change Set: 8a5023febd29
Released: Apr 4, 2014
Updated: Jul 4, 2014 by Ptools
Dev status: Beta Help Icon

Recommended Download

Application NTVS Beta VS 2013.msi
application, 2744K, uploaded Apr 1, 2014 - 19694 downloads

Other Available Downloads

Application NTVS Beta VS 2012.msi
application, 2744K, uploaded Apr 1, 2014 - 3259 downloads
application, 87351K, uploaded Apr 5, 2014 - 609 downloads

Release Notes

update - we highly recommend using this devbuild which has numerous fixes in it instead:

Please see important note regarding memory usage/crashes below

NTVS 1.0 Beta release notes Apr 04 2014

Node.js Tools for Visual Studio is a plug-in (Apache 2.0) that turns VS into a node.js development environment.

NTVS is available for:

  • Visual Studio 2013 Express for Web -- New for Beta
  • Visual Studio 2013 Pro or higher
  • Visual Studio 2012 Pro or higher

NTVS supports the following:

  • node projects
  • Intellisense
  • Debugging (local & remote with support for Linux and MacOS)
  • Edit and Continue -- New for Beta
  • Profiling
  • node REPL with multi-line editing
  • Integrated npm GUI -- Redesigned for Beta
  • TypeScript (IntelliSense, Debugging, Profiling, Unit Test) -- New for Beta
  • Jade syntax highlighting -- New for Beta
  • Test Explorer integration -- New for Beta
  • Azure Web Sites
  • Azure Web Sites Remote Debugging -- New for Beta
  • Azure Cloud Service - Web Role
  • Azure Cloud Service - Worker Role -- New for Beta
  • Git publishing

New Demo Videos:

Known Beta limitations:

  • IntelliSense uses large amounts of memory on medium/large projects which can result in crashes and instability - you can turn off completions in Tools/Options/Text Editor/Node.js/Statement completion/Auto list members to avoid this (recommended). We are working on a fix. Sorry about this.
  • IntelliSense fails on large projects (JS lang service timeout issue)
  • Interactive Window (REPL): No IntelliSense
  • Max Path issues - Place projects in a short path such as c:\code, not the default VS Projects location
  • Azure Web Site Remote Debugging - Server Explorer command is not available unless VS 2013 Update 2 RC or later is installed.
  • Debug -> Attach to Process is not available on Visual Studio Express for Web. This means that regular remote debugging is not available on Express for Web at all, and Azure remote debugging is available for NTVS only with Update 2 RC or later.
  • npm package manager dialog may leave a modal operation running after the dialog is closed. When this happens you'll experience strange keyboard behavior and a prompt when trying to close VS.
  • npm global modules item in solution explorer is not functional, it will not list any of the global modules. However, you can use the package manager dialog to install modules globally.

For a more detailed list, please see the Issues tab.


NTVS was developed by the same team that brought you PTVS and a few friends - namely Bart Read from red-gate (npm GUI), and Dmitry Tretyakov from Clickberry for several debugger fixes & features. We'd like to thank everyone who helped test the pre-Alpha version as well.

Reviews for this release

Makes VS very Slow. I'm running win 8.1 with 12 GB of ram and a i7 processor. Takes about a minute to open the solution and clicking around is overall slow. CPU is constantly on 50% and RAM is about 3 GB for VS. Perhaps this is related to running Resharper and Web Essentials together with NTVS - not sure.
by abergs on May 27, 2014 at 2:09 PM
It's getting better and better release by release, but VASH syntax highlighting support will be a huge plus! Are you going to support vash syntax highlighting?
by davidlars99 on May 20, 2014 at 3:32 AM
I love this plug-in and the features that were added in the beta are great. However, the beta release also comes with a massive performance hit to a point where it is almost unusable. My VS with the Alpha installed uses about 600MB on startup, with the beta installed it's using over 1.6GB. I've also tried the May 14th build release as well.
by Kaman on May 22, 2014 at 4:28 PM
Unfortunately, Visual studio become very slow when I use this plug-in (tested on different computers) For information we work on "" project (MongoDB ExpressJS AngularJS node.js) I hope this will be solved for the release version because this plugin is exactly what I need
by Ciprio on May 22, 2014 at 9:21 AM
Ciprio - can you try the latest Dev build? thanks!
Reply by Ptools (N/A) on May 22, 2014 at 3:57 PM
Installation went well and demo projects build/run as expected. However, I'm getting an error that I have not seen before install NTVS. The error is coming from VS that an extension caused an error and it's logged in ActivityLog.xml. Previous to installing NTVS I installed Typescript a couple weeks ago. This error would occur at VS startup every time. Today I uninstalled NTVS and reinstalled it. VS startup is now without error. The I created a Typescript project of type Node.js Web. Now I'm getting the VS extension error again, but only when I open a Typescript Node.js project. Error message is too large to paste here. Is there an dependency on installation sequence with Typescript?
by tonylong on Jul 1, 2014 at 9:27 PM
There shouldn't be such a dependency (nor even a requirement that TS be installed at all, if you're not using the corresponding project type). Please file a bug for this at - it allows for a significantly longer description there, and to attach files to tickets.
Reply by pminaev (N/A) on Jul 1, 2014 at 9:55 PM
I have just installed Visual Studio 2013 Professional followed by the node plug-in. Although I must agree with most others that it looks very promising, it does crash each and every time I try to run a (wizard generated) express application (it opens the browser, shows the wizard generated page, and then VS crashes). I then tried to install VS 2013 Express for the Web on my laptop, and this gives unfortunately the same result. The eventlog shows two entries, and Application Error and a .NET Runtime error ( ved System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__5(System.Object) ved System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) ved System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) ved System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) ved System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() ved System.Threading.ThreadPoolWorkQueue.Dispatch() ved System.Threading._ThreadPoolWaitCallback.PerformWaitCallbac
by plaul1 on Jun 27, 2014 at 12:12 PM
Thanks for fixing the TypeScript tests! I hope the team will hold back on adding any further new features and instead focus on making the existing feature set more stable.
by nabog on Jun 26, 2014 at 10:22 AM
thx nabog - we've added a beta2 and it'll be all about stability & larger app support. we won't go to RTM until the community gives it a thumbs up. the issues are with JSLS and we're working w them on a solution.
Reply by Ptools (N/A) on Apr 7, 2014 at 8:24 PM
Excellent tool . One feature that is very important and missing , is to be able to analize and existing v8.log that was created somewhere else. This is a very important feature when you need to profile something that happened with a customer .
by rino65 on Jun 18, 2014 at 7:50 AM
Very nice release, I used it all weekend. although it crashes a lot while debugging. I had numerous times it restarted itself. Still better than what I was using. just wish it did not crash as much. nice add-on. good features
by Donsw on Jun 16, 2014 at 8:30 PM
Experiencing problems with Resharper and WebEssentials, as mentioned by others. - RAM 2-3 GB Keyboard & Shortcuts: - Code commenting doesn't work. - Code identation doesn't work. + Ident on semi-colon works
by gr9zev on Jun 4, 2014 at 12:56 PM
With this version, my debugger detaches when an error occurs. Same problem with the latest dev version. 1.0 Alpha nicely keeps the debugger attached and thus jumps to the location of the error and provides a call stack/locals. **UPDATE** @pminaev: All exceptions were disabled. Enabling them solved my problem. Awesome, thanks!
by gjkunst on Jun 3, 2014 at 5:19 PM
This is actually an option that you can set in Debug -> Exceptions, for any error, or for specific error types. Can you check that the types you want VS to stop and report on are checked appropriately in that dialog?
Reply by pminaev (N/A) on May 30, 2014 at 4:16 PM
Node finally gets a great development experience! I can develop and debug in Visual Studio, check-in to TFS, then deploy to any node-enabled target: Windows, Linux, Azure. Awesome!
by johndpalm on May 29, 2014 at 7:15 PM
Awesome! Works like a charm! No performance issues here at all. Using VS 2013 Express for WebDev.
by Nightking on May 27, 2014 at 3:57 PM
Vs startup time has increased extremely, >30s for a small project (2 js/ts files) on a I7 with 24 gb, otherwise good! thanks for making typescript available!
by hansrwindhoff on May 23, 2014 at 4:09 PM
Fantastic interface. Easy. The desire to explore all of what the NPM world has to offer, has just multiplied.
by rudyhinojosa2007 on May 21, 2014 at 3:29 PM
This was the missing link! Git, Azure, Node.js, and Bootstrap - I can now develop with all of them together in VS2013! Awesome!
by HaroldFredShort on May 21, 2014 at 7:31 AM
Please keep up the good work on this plugin. The Intellisense features are a huge plus. I'm coming from Emacs + Evil (vim emulation package) and the VS Intellisense outperforms anything available for emacs. NTVS + VsVim = awesome.
by strobot on May 12, 2014 at 1:18 AM
Excellent work! You have taken so much of the headache out of node application development.
by poseidonCore on Apr 30, 2014 at 10:50 AM
Great to see VS supporting non-Microsoft technologies, keep it up! If only VS came to Mac OS and Linux.. One can dream. My only complaint is that it gets unstable on a brand new ultrabook after a while, but you guys seem to be on top of that already. With that out of the way, this will easily be my tool of choice for node projects.
by Bicubic on Apr 23, 2014 at 10:41 AM
As a net developer (forced to move to the new Angular world) I have been boiler plating with yeoman and the full stack generator. I even was considering purchasing Jetbraings WebStorm (the best of the best) to develop in Node (because of mongoose ). now i went back to my beloved Visual Studio and I feel right at home with node.js. working on the MEAN stack is now painless.. Thank you for this amazing tool. It will certainly make us way more productive. yes is not perfect, but is better than using Sublime text. and i am sure it will become perfect eventually .
by oscar_agreda on Apr 9, 2014 at 4:03 AM
In Web Express, it is impossible to use the profiling tools (is it missing Visual Studio Profiler Reporting Tools?). Also, when importing a project that did not have a package.json, but does have a `node_modules` directory, the application did not seem to run and internal details of the extension were shown. And it seems it is required to create a solution and project for debugging a simple script.
by HAH on Apr 8, 2014 at 2:25 PM
Hi HAH - it's true that some features are not available in the free version of VS. that is unfortunately out of our hands. Profiling is one of them and I wish it was available to everyone. VS is generally "project" based. In PTVS we've added the support to just open a script & run/debug. it's on the TODO list for NTVS.
Reply by Ptools (N/A) on Apr 9, 2014 at 5:17 PM
Lot's of new functionality I didn't really care about, significantly less stable. No longer able to inspect by flying over a value when debugging locally (can still do a watch). Javascript dies within 10 minutes of editing in almost every session (even with "Auto list members" turned off, which is necessary to avoid having it hang/crash even sooner). Approximately 50% of sessions end with a 60 second hang, crash, and spontaneous restart of VS (with accompanying loss of edits). Most frustrating is that all I'm doing to cause all of this is typing code. I'd go back to the alpha and wait for an RC if I could. Maybe it works better if you have a small/simple project. Anyway, be warned. I love the project in general, and if it didn't constantly crash, I'd give it 10 stars.
by RDD3 on Apr 5, 2014 at 10:10 PM
rdd3 - totally bummed that you're having a bad experience. we'd like to fix the issues asap. can you possibly share your solution with us? if so, pls send to regarding the memory/crashes - we're aware of of the issue with JSLS and are working w them on a solution. if it doesnt pan out fast enough, we'll investigate other options, such as writing our own JS analysis engine. meanwhile i'll create a bug report w your issues for tracking purposes. so apologies, hang (bad pun) in there & we'll fix as many of the issues as we for beta2 (check devbuilds for earlier releases).
Reply by Ptools (N/A) on Apr 5, 2014 at 11:00 PM
I don't understand what is Microsoft's recommended approach for web development these days. Are we supposed to forget ASP.NET MVC and C# and move to Node and JS for every scenario? Why isn't there a comparison of pros and cons on the front page? Get your story straight.
by dsaf on Apr 9, 2014 at 9:56 AM
dsaf - there is no /one/ true way. each language/runtime/framework has its pluses or minuses. support for node.js, python, java, ruby, etc. on Azure simply means that customers want to use these technologies and we're gradually adding SDK and VS support for some of them. adding a table that lists what technology is aimed at what scenario is a good idea. it would be best on the main Azure website, not here on NTVS's homepage probably. will let them know. thx.
Reply by Ptools (N/A) on Apr 9, 2014 at 5:26 PM
A lot of new features I wasn't interested in. Build and run multiple projects is the only new feature I wanted, which now works. Also it's only available in VS 2013. The Beta seems more unstable. The NPM manager seems worse. Unfortunately my build fails, and I've had to revert to the Alpha. The issue is "Unreadable Stream". The issue crashes the VS IDE.
by GerardDownes on Apr 8, 2014 at 4:29 PM
Gerard - sorry about that. re being unstable - we're aware of the issues w JSLS and are working on a fix. re NPM can you be more specific or provide repro steps? same with the build fails issue? much thx.
Reply by Ptools (N/A) on Apr 9, 2014 at 5:28 PM