NTVS 1.0 RC

Rating:        Based on 10 ratings
Reviewed:  9 reviews
Downloads: 8331
Change Set: 83e0615160ca
Released: Nov 24, 2014
Updated: Dec 16, 2014 by mousetraps
Dev status: Beta Help Icon

Recommended Download

Application NTVS 1.0 RC VS 2013
application, 5960K, uploaded Nov 24, 2014 - 7486 downloads

Other Available Downloads

Application NTVS 1.0 RC VS 2012
application, 5960K, uploaded Nov 24, 2014 - 845 downloads

Release Notes

We are pleased to announce the release of Node.js Tools 1.0 RC for Visual Studio.

Node.js Tools for Visual Studio (NTVS) is a free, open-source plug-in that turns Visual Studio into a Node.js Integrated Development Environment (IDE). It supports a broad range of features including editing, IntelliSense, cross platform and remote debugging, edit and continue, npm integration, profiling, TypeScript, and an integrated REPL window. NTVS also includes a list of project templates that make it easy to quickly create and deploy websites to Microsoft Azure Websites or Cloud Services.

NTVS 1.0 RC is available for:

Changes since Beta 3

Improved npm integration

The npm UI now supports per-project .npmrc files, so you can switch seamlessly between registry configurations and collaborate more easily with your team. We have also added an ‘Open Folder in Explorer’ context menu command to npm package nodes in solution explorer so that you can browse more quickly to the associated directory in node_modules.

Additionally, many npm UI performance and stability issues have been fixed in RC, so be sure to give it a try if you were having trouble in earlier releases.

Improved code formatting and editing

We have made several improvements to code formatting and editing experiences (including comments, function indentation, control flow, and auto-complete.)

Numerous bug fixes

Numerous issues have been fixed all across the product. We expect the RC release to provide both a much better user experience and improved stability. We would like to thank all of the people who took their time to report issues, send feedback for this release. We very much appreciate your help!
  • andrees, avidmost, bdegreve, bkramer, davegordon, edvinv, flightly_bravo, frankyboy, gkirkpatrick, henrikarapuu, ivan1111, jhowe11, lelong37, maer, nabog, rajatmig29, sammons, schlott, stkb, tbarros, thedeeds, thesowee, ts330, undeadbane, vilic, waynebloss

Help Make NTVS Better

NTVS is an open source project and we’re always willing to take high quality contributions. If you’d like to contribute, please check out our issue tracker for outstanding bugs and features which can be implemented. You can also help make NTVS better by reporting issues or helping out your fellow users on our forums.

Reviews for this release

     
this is a great release. Most stable one so far. Crashing when removing break points doesn't seem to be an issue - load times are much faster - intellisense finally works. Auto formatting is still a pain. I use with TeamFounation - binding seems to finally work without having to manually bind new projects. Using VS 2012, VS 2013 Pro and Developer.
by kevinbarnett5506 on Dec 15, 2014 at 7:34 PM
     
I am fairly new to web development (I'm used to making C# desktop applications) and this extension has made using Node and AngularJS quite easy. There may or may not be better IDEs out there for javascript, but I picked this extension because I'm used to Visual Studio. The ability to open the command prompt from visual studio and the node package manager are very nice. However, I have to take a star off because of a few issues. One issue is that visual studio will occasionally lose focus while typing. I suspect it has something to do with the Node code analysis, since I only lose focus when there is something about Node code analysis in the status bar. Another issue I have is the random crashes. It's not too bad, but I usually experience them at least once per day. I usually code for multiple hours, so one crash per day isn't a lot but it can be annoying at times. I have been unable to reproduce the crashing. If you are able to put up with these two minor issues, I would highly recommend using this extension.
by hillshiya on Dec 15, 2014 at 12:47 PM
HI hillshiya, thanks for the feedback. We're working hard to iron out all the instability issues before the next release. I understand you can't reproduce the issue, but would you mind taking a look at the windows event log (event viewer) and supplying us with the relevant logging info? Also we've fixed a lot of issues recently, so it would be awesome if you could check out the latest dev build and verify that stability has improved for you. http://nodejstools.codeplex.com/releases/view/181775 Additionally, you mentioned you're a C# dev... you don't happen to have resharper installed, do you? We've run into some issues due to their extension recently because they run on all project types, not just c#/vb. For instance, https://nodejstools.codeplex.com/workitem/1584
Reply by mousetraps (Coordinator) on Dec 15, 2014 at 4:45 PM
     
Lots of great functionality but I've wasted hours trying to get the basics working. I take a vanilla Express package and deploy it to Azure fine. When I generate the same vanilla Express package as a nodejs express project using NTVS, it doesn't deploy properly (seems like npm isn't pulling in dependencies from package.json). Debugging info is minimal/not useful UPDATE: Many hours of web trawling and experimentation later, I've gotten this working. Here were the steps that weren't evident to me. Perhaps these would've been obvious to experienced Azure/node devs -- as a newbie these stumped me 1) Update my build definition to * use project instead of SLN * use /t:Package 2) Manually run npm install by creating installPackages.bat (why?) 3) Add workaround for NPM bug: create NPM folder and make sure it's writable: md C:\Users\buildguest\AppData\Roaming\npm 4) Manually publish! I'd assumed that continuous deployment via VSO auto-published for me - this wasn't true. I had to manually publish once after which continuous deployment worked to update 5) Add workaround to web.debug.config: interceptor="--debug "%ProgramFiles(x86)%\iisnode\interceptor.js&quot"
by db11235 on Dec 12, 2014 at 5:39 PM
     
I have VS2013 Express. Just upgraded VS2013 to update 4. I downloaded and tried to install the NTVS1.0 for VS2013 and I get a message that this version of Visual Studio is not supported. The site mentions that it works with VS2013 express update 2 or later and I'm on update 4 with a fresh install.
by Mandr4ke on Dec 3, 2014 at 8:47 AM
Are you using Express Desktop or Express Web? NTVS only supports Express Web currently. You might also want to check out the new Community Edition.
Reply by dinov (Coordinator) on Dec 3, 2014 at 6:49 PM
     
I mean if it crushes all the time, I can't give it more than one star. Wasting my time on this for two days, not feeling comfortable working with it thinking all the time, oh, is it gonna crush now!? definitely worst package for VS highly not recommended!
by Uloga on Dec 2, 2014 at 6:25 PM
Hi Uloga, sorry to hear you're having a bad experience. We would love to fix the crashes you're running into asap, but unfortunately we don't have enough info to diagnose the issue. Have you been able to reproduce the crashes at all, or is it seemingly random? Would you mind filing an issue with your Diagnostic Info (Tools > Node.js Tools > Diagnostic Info...) as well as the event logs from the crashes? (Windows Event Viewer)
Reply by mousetraps (Coordinator) on Dec 2, 2014 at 11:06 PM
     
too many crashes
by vclteam on Dec 2, 2014 at 4:23 PM
Hi vclteam, we would love to fix this asap. Would you mind providing more info? Have you been able to reproduce the crashes at all, or is it seemingly random? Would you mind filing an issue with your Diagnostic Info (Tools > Node.js Tools > Diagnostic Info...) as well as the event logs from the crashes? (Windows Event Viewer).
Reply by mousetraps (Coordinator) on Dec 2, 2014 at 11:04 PM
     
Integrated with VS Community perfectly for me. I hope that the final release will give TypeScript the recognition that it deserves. Well done.
by poseidonCore on Nov 27, 2014 at 11:03 PM
     
Keeps getting better. The "Open folder in File Explorer" for npm folders is very useful.
by nabog on Nov 25, 2014 at 6:13 PM
     
A great tool. node.js + NTVS + TypeScript makes for a very productive development system. Very stable too. I've had VS crashing recently, but that turned out to be caused by WebEssentials, not NTVS.
by yortus on Dec 3, 2014 at 12:43 AM