Created Unassigned: switch indent [1809]
switch (x) { case:};And I want to:switch (x) {case:};
View ArticleCommented Unassigned: Breakpoints are not working with VS 2014 Update 4 and...
I have tried starting a project from the "Blank Node.js Console Application" and "Blank Node.js Web Application" projects. When I place a breakpoint and then press F5, the application is executed, but...
View ArticleCreated Unassigned: Basic JavaScript intellisense stopped working after...
Hi, I am using VS 2013 update 3. After installing Node.js Tools (NTVS 1.0 RC 2 VS 2013). My basic JavaScript intellisense stopped working. I have to press ctrl+space every time to display hints....
View ArticleCommented Unassigned: Basic JavaScript intellisense stopped working after...
Hi, I am using VS 2013 update 3. After installing Node.js Tools (NTVS 1.0 RC 2 VS 2013). My basic JavaScript intellisense stopped working. I have to press ctrl+space every time to display hints....
View ArticleCommented Unassigned: doskey crash [901]
Whenever I try to use Node.js Tools I get a crash on doskey.exe. This happens when I create or open a Node project and when I open the npm tools. I did not try any other node tools features.When I...
View ArticleCommented Issue: Are @scoped npm packages supported? [1607]
Hi,I'm using VS 2015 preview 1 with NTVS RC 1. I am using a private npm repository (npm Enterprise, see: https://docs.npmjs.com/enterprise/intro) which allows me to install @scoped packages which are...
View ArticleCommented Unassigned: 100% CPU usage for very long periods (system unusable)...
As long as I have one single Node.js project open in VS, the CPU hits 100% and stays there for prolonged periods, making the complete Windows desktop unusable.CPU usage will eventually drop to 50%-60...
View ArticleCommented Unassigned: 100% CPU usage for very long periods (system unusable)...
As long as I have one single Node.js project open in VS, the CPU hits 100% and stays there for prolonged periods, making the complete Windows desktop unusable.CPU usage will eventually drop to 50%-60...
View ArticleCommented Unassigned: 100% CPU usage for very long periods (system unusable)...
As long as I have one single Node.js project open in VS, the CPU hits 100% and stays there for prolonged periods, making the complete Windows desktop unusable.CPU usage will eventually drop to 50%-60...
View ArticleEdited Issue: Version not supported error when using chocolatey shim for...
When using the chocolatey nodejs.commandline package, it generates a shim in `C:\ProgramData\chocolatey\bin\node.exe`. After upgrading to the current version of node.js tools (1.0 RC2), it picked that...
View ArticleEdited Issue: Setting the node.exe path in properties does not also set npm...
Currently if the user sets the path to the node.exe they want to use in node.js project properties, we don't adjust the path to NPM and possibly other things. We should look at taking this property...
View ArticleEdited Unassigned: open old project on VS 2013 error when update NTVS 1.0 RC2...
E:\MEAN\Poll\VoteOnline\VoteOnline.njsproj : error : The project file 'E:\MEAN\Poll\VoteOnline\VoteOnline.njsproj' cannot be opened.There is a missing project subtype.Subtype:...
View ArticleCommented Unassigned: open old project on VS 2013 error when update NTVS 1.0...
E:\MEAN\Poll\VoteOnline\VoteOnline.njsproj : error : The project file 'E:\MEAN\Poll\VoteOnline\VoteOnline.njsproj' cannot be opened.There is a missing project subtype.Subtype:...
View ArticleReleased: VS2015 CTP 5 Dev Build (02-13-15) (Feb 16, 2015)
Note: The VS 2015 build requires Visual Studio 2015 CTP 5 and is probablyhighly unstable. See source code history for information about recent fixes. Please report any bugs that you find in this build,...
View ArticleUpdated Release: VS2015 CTP 5 Dev Build (02-13-15) (Feb 16, 2015)
Note: The VS 2015 build requires Visual Studio 2015 CTP 5 and is probably highly unstable.See source code history for information about recent fixes.Please report any bugs that you find in this build,...
View ArticleReleased: 02-13-2015 Dev Build (Feb 16, 2015)
This build fixes the profiling and debugging issues experienced after the Node.js v0.12.0 api change (among other things) See source code history for information about recent fixes. Please report any...
View ArticleUpdated Release: 02-13-2015 Dev Build (Feb 16, 2015)
This build fixes the profiling and debugging issues experienced after the Node.js v0.12.0 api change (among other things)See source code history for information about recent fixes.Please report any...
View ArticleNew Post: Please consider moving this project to GitHub
Build issues fixed and new dev builds are up!
View ArticleCommented Unassigned: Basic JavaScript intellisense stopped working after...
Hi, I am using VS 2013 update 3. After installing Node.js Tools (NTVS 1.0 RC 2 VS 2013). My basic JavaScript intellisense stopped working. I have to press ctrl+space every time to display hints....
View ArticleReleased: 02-13-2015 Dev Build (Feb 16, 2015)
This build fixes the profiling issues experienced after the Node.js v0.12.0 api change (among other things) See source code history for information about recent fixes. Please report any bugs that you...
View Article