Reviewed: 01-29-2015 Dev Build (Feb 06, 2015)
Rated 4 Stars (out of 5) - no VS crashes, though intellisense stops working occasionally (left my solution open all night, no intellisense in the morning) However, I can't see any benefits of this...
View ArticleNew Post: NodeJS tools for non Node-JS project
I think the VS tools should work in ANY project type that has a node_modules directory. My specific case is a C# project that has TypeScript items in it. I don't see there being a need for a special...
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 ArticleNew Post: NodeJS tools for non Node-JS project
Gotcha - unfortunately implementing the solution explorer UI wouldn't wouldn't be as simple as enabling it for other project types because NTVS is based on MPFProj, which is a different project system...
View ArticleNew Post: Please consider moving this project to GitHub
Thanks nabog! We actually didn't realize GitHub had inline images in issues or binary releases, which was one of our sticking points. This inspired me to go back and research other "sticking points"...
View ArticleEdited Issue: .npm in interactive windows doesn't recognize the project [1770]
NTVS: 30109.03 Repro:1. Create a Node.js Azure service solution.2. Add a web role and a worker role so you have 2 projects in the solution.3. Open the Node.js Interactive window4. In the interactive...
View ArticleEdited Issue: .npm -g install doesn't work when no default project [1796]
should be allowed to use -g at beginning of npm command
View ArticleEdited Issue: Installing without file associations still installs file...
At least the .njsperf association, and not the .njsproj association.
View ArticleCreated Issue: Unable to profile with io.js [1798]
Config:- Win8.1 ENU- io.js- VS2013.4 Community- NTVS 30129.00Repro:1. Create a starter Azure Express 3 web app under c:\ntvs2. Select Analyze->Profile (nodejs)3. Close the website after it...
View ArticleEdited Issue: Installing without file associations still installs file...
At least the .njsperf association, and not the .njsproj association.
View ArticleCommented Issue: Unable to profile with io.js [1798]
Config:- Win8.1 ENU- io.js- VS2013.4 Community- NTVS 30129.00Repro:1. Create a starter Azure Express 3 web app under c:\ntvs2. Select Analyze->Profile (nodejs)3. Close the website after it...
View ArticleCommented Issue: Weird project refresh issue [1793]
Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a...
View ArticleCommented Issue: Weird project refresh issue [1793]
Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a...
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 Issue: Weird project refresh issue [1793]
Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a...
View ArticleCommented Issue: Weird project refresh issue [1793]
Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a...
View ArticleCommented Issue: Weird project refresh issue [1793]
Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a...
View ArticleCommented Issue: Weird project refresh issue [1793]
Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a...
View ArticleCommented Issue: Weird project refresh issue [1793]
Don't know how it happened, but VS2013 + NTVS RC2 got itself in a tizzy, and the project as a whole kept trying to refresh itself, over and over. An obvious manifestation of this was if I expanded a...
View Article