Node.js Tools for Visual Studio 1.0 Beta 2 Available

Node.js Tools for Visual Studio 1.0 Beta 2 Available

Rate This
  • Comments 20

Today we released the Node.js Tools for Visual Studio 1.0 Beta 2 which is now available for download.

NTVS is Microsoft’s free Visual Studio add-on that enables a rich experience for working with Node.js apps, giving developers the power of the Visual Studio code editor including support for IntelliSense, the Visual Studio debugger, and for running Node.js apps on Microsoft Azure Web Sites or Cloud Services.


Here are the highlights in today’s release:

  • New analysis and IntelliSense engine. We created a new IntelliSense engine which is capable of analyzing much larger code bases. Once processed the results of the analysis are cached and reused in subsequent sessions which leads to much better performance compared to our previous release. The new engine is also configurable so you can change how aggressively it works or completely turn it off using the Tools option menu (Tools > Options > Text Editor > Node.js >IntelliSense).
  • Improved NPM UI. We updated the NPM management UI so it is easier to use. We’ve also added integrated support for invoking NPM inside of the REPL window with a new .npm command.
  • Mocha unit test support. We expanded unit test support to include using tests written with Mocha JavaScript test framework.
  • Custom unit tests. You can now add support for your own unit test frameworks by writing a single Node module that will find and run the tests.

We’ve also fixed numerous bugs. See our full release notes for all the details and please send us your feedback through our forum.



Shahrokh Mortazavi Shahrokh Mortazavi, Partner Program Manager, Visual Studio Cloud Platform Tools

Shahrokh Mortazavi currently works in the Developer Division of Microsoft on Python and Node.js tool chain. Previously, he was in the High Performance Computing group at Microsoft. He worked on the Phoenix Compiler tool chain (code gen, analysis, JIT) at Microsoft Research and for 10 years led Sun Microsystems’ Code Generation & Optimization compiler backend teams.

Leave a Comment
  • Please add 7 and 3 and type the answer here:
  • Post
  • Who can understand Microsoft ?

    You'll support Node.js, which isn't really necessary - we've all being using JavaScript and Node.js without Microsoft.

    But you won't support Microsoft's own VB6 Visual Basic programming language ?

    Where do your priorities lay ?

    Large organisations throughout the world have applications developed with VB6 programming but you ignore them ?

    You refuse to open source the VB6 programming language.  You refuse to bring back an updated version of the Visual Basic 6 programming language. You refuse even to sell copies of VB6 to those who have existing VB6 code to support.

    But you waste time bringing out Node.js.  We don't need Microsoft for that.

  • Oh, if only there were a way to vote down another person's comment as unhelpful...

  • This is great! I hope microsoft will continue in this direction.

  • I think this is awesome! I don't use node.js myself, but the fact that Microsoft is officially developing tooling for other, open source, projects is really great and is very promising for the future of Visual Studio, the one IDE to rule them all!

  • Nice job MS. Are you also going to support more Javascript or web-based frameworks and tools? Support for AngularJS, Bootstrap, SCSS (perhaps with compilation?) or MongoDB?

  • Man, MSFT is so lost.

    They are just wasting manpower to support every open source project out there, instead of creating there own vision/framework to solve the problem.

    Microsoft did not waste time to support PHP, instead they created ASP and then ASP.Net which as lead to amazing MVC, Web API etc.

    Like someone commented, there are tools/IDEs (Eclipse ??) out there already to do open source development.

    And like your CEO said, MSFT is a platform company, so stop developing support for pesky open source tools (python, ruby, node, angular etc), and wear your game hat to create msft solutions to compete with Angular, WordPress that work well on msft stack.

    What incentive do i have to use microsoft frameworks and tools when you support open source once just as good ??

  • Very nice... Now I need to give Visual Studio a try :)

  • I don't agree with those that say this is a waste, but do agree that it's pretty lame that you do this and claim not to have resources for other MS stack tech that we have invested in, .Net is in need of a refresh, isn't it clear yet that the we aren't interested in the Metro/Com+ stack, does the fact there are less than 100 descent store apps cause any concern? when will the sinofsky nightmare come to an end? what would MS do if one of there vendors ignored them for 4 years?

  • @VB6er

    >> we've all being using JavaScript and Node.js without Microsoft.

    I don't know about "all", but Visual Studio's NodeJs is the best environment I've ever tried. Even some diehard Mac worshipers tell me they do they're NodeJs coding on Windows machines because VS-plus-NodeJs is so good.


    >> create msft solutions to compete with Angular, WordPress that work well on msft stack.

    With all the people and money that Microsoft has at its disposal, it should have no problem to "create solutions". The problem is selling the solutions. The problem is Linux vs Windows war. For each Windows web developer, there are 3,000 Linux web developers. Therefore, it's a good thing for Microsoft and developers that Microsoft supports NodeJs.

  • Nice update by MS


  • @socrates The previous MSVS node tools were just awful. Trying doing any serious development with them and you would have seen the shortcomings. Crashes, slow, incorrect intellisense, poor integration.

    I am pleased they have got round to another release and I'll give it a go again, but in the meantime WebStorm is a great tool.

  • Now if only would come back. I want my bots. :(

  • I thinks that great. I recently started to learn node.js and i got this good news.

    Thanks and Regards


  • I was excited for this until I realized it required a special project type. I understand the need for that kind of sandbox in development, but if there any chance we'll see the functionality on a more global scale in the future?

    Honestly, all we need is for npm_packages to be recognized as a special folder, and to have a straight up pure npm command line within Visual Studio. Take a look at WebStorm, from JetBrains. They do it very, very well.

    I'm not discounting how good this is. But I was excited because I want just more conveniently use node.js to run and compile things against my MVC site, like grunt and such. I can still do that with a simple power shell, but being baked into visual studio and having project relative path had me kind of excited.

  • I don't feel this is a waste at all. It just isn't what I personally wanted. I think this is a very healthy step in general.

Page 1 of 2 (20 items) 12