New Comment on "Debugging"
I can confirm that 0.10.26 resolves the debugging issues found in 0.10.25 (it could not break on exceptions. now it does)
View ArticleNew Comment on "Debugging"
I can confirm that 0.10.36 resolves the debugging issues found in 0.10.25 (it could not break on exceptions. now it does)
View ArticleNew Post: NodeJS tools for non Node-JS project
Hi wasabi, would you mind elaborating a little on your use case (project type, scenario, etc.) and exactly what NTVS features you want to enable? Are you looking for something similar to ASP.NET...
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: JSLint.VS2013 go-to-line problem [1792]
I use the JSLint.VS2013 extension quite a lot.It's probably not the fault of NTVS, but I note that clicking or double-clicking on a reported message fails to go to the line in question, in the editor....
View ArticleNew Post: Please consider moving this project to GitHub
Nice to read this feedback re. the state of the project. I'm just getting started with MEAN stack on Windows (after years with C# and ASP.NET MVC), and have spent some time checking out different tools...
View ArticleNew Post: Please consider moving this project to GitHub
@mousetraps, I'm really glad to hear the reassurances - so thanks for that! Moving to github means we have to find suitable replacements for or build new processes GitHub does all that out of the box -...
View ArticleCreated Unassigned: High memory usage [1795]
I'm using the latest release (NTVS 1.0 RC2) and as well as seeing high CPU usage from time to time coming from Visual studio I am also seeing very high memory usage (see attached)The longer I use VS...
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: High memory usage [1795]
I'm using the latest release (NTVS 1.0 RC2) and as well as seeing high CPU usage from time to time coming from Visual studio I am also seeing very high memory usage (see attached)The longer I use VS...
View ArticleCreated Issue: .npm -g install doesn't work when no default project [1796]
should be allowed to use -g at beginning of npm command
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 ArticleCreated Unassigned: WAT070: The referenced assembly WorkerRole.exe was not...
Attempting to build an Azure Cloud Services project via MSBuild omits the following error. As far as I was aware the Worker Role (Nodejs) projects do not generate an executable file.Any ideas how I can...
View ArticleEdited Unassigned: WAT070: The referenced assembly WorkerRole.exe was not...
Attempting to build an Azure Cloud Services project via MSBuild emits the following error. As far as I was aware the Worker Role (Nodejs) projects do not generate an executable file.Any ideas how I can...
View ArticleEdited Unassigned: WAT070: The referenced assembly WorkerRole.exe was not...
Attempting to build an Azure Cloud Services project via MSBuild emits the following error. As far as I was aware the Worker Role (Nodejs) projects do not generate an executable file, nor can I find any...
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 ArticleReviewed: 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 Article