Superb stuff. Now time for MS to help getting io.js working on Windows. With confidence.
Node.js Tools for Visual Studio
41–50 of 127 posts
Re: Node.js Tools for Visual Studio
#42Dev here - happy to answer any questions you have :)
Ooh, tracepoints, DO WANT! Are they only available in one of the paid versions of Visual Studio? The VS debugger is excellent, its probably the dev tool I miss the most since leaving C++ and going to JS, and tracepoints are the feature I wish for most frequently in a browser debugger. So I was about to naively suggest the VS team could push for tracepoints in IE, but OMG! Tracepoints are in IE11. Where have I been? I…
We've got breakpoints, conditional breakpoints, tracepoints... All the points, really ;-)
I don't think you need one of the paid versions, but I'll double check and edit this if I'm wrong.
Re: Node.js Tools for Visual Studio
#43Earlier quoted context omitted.
Wow this looks pretty amazing! How do you handle the super-long paths npm is so fond of? On Windows I often run into issues when searching or trying to manipulate a solution containing anything npm due to too-long paths.
I have run into this problem as well. Manually modifying packages is not fun.
See my comment above, but if you do this frequently... we have a feature that enables you to right click on an installed npm package in the npm tree in Solution Explorer and open the relevant folder in explorer
Re: Node.js Tools for Visual Studio
#44Superb stuff. Now time for MS to help getting io.js working on Windows. With confidence.
What are the issues with running on Windows? These tools support io.js
https://nodejstools.codeplex.com/wikipage?title=io.js
Re: Node.js Tools for Visual Studio
#45This is great news, but aren't there bigger fish to fry with really supporting node.js & npm on Windows? The 255 character path limit bug has been around for a long time and still unresolved/broken on Windows (see https://github.com/joyent/node/issues/6960 and https://github.com/npm/npm/issues/5641). Suggestions to fix it on the Windows side have been closed too: http://visualstudio.uservoice.com/forums/121579-visual-studi... Would be nice for people to stop throwing it around like a hot potato and fix it for good. Although it sounds like an edge case, it's actually really common for some libraries to his this limit and be unusable on Windows.
Re: Node.js Tools for Visual Studio
#46How many people do you think will actually use this? I just really cannot ever see mass use of azure and visual studio in the web ecosystem. The people writing nodejs code are all using vim and unix, and you're asking them to give up their workflow and change operating systems. I want to be able to poke around in bash. (edited back in) Sure, some people new to web programming might go this route. But the next big web…
I think your original comment mentioned that you'd want console access. While I was grabbing a screenshot, it looks like you edited your comment and removed that, but I think that was a valid concern. There's a web based console that's sadly not that well known. Here's a screenshot: http://i.imgur.com/Lrw7lL1.png Here's a video showing more of the features (it's from 2013, it looks better and more has been added sinc…
Jon, this is something which should really be better promoted. I follow most of the interesting .net peeps on twitter & have listened to Scott H's pod + Herding Code for years.
This is the first time I've seen this, which is a shame, because it solves a lot of my misgivings with Azure..
Re: Node.js Tools for Visual Studio
#47Earlier quoted context omitted.
Wow this looks pretty amazing! How do you handle the super-long paths npm is so fond of? On Windows I often run into issues when searching or trying to manipulate a solution containing anything npm due to too-long paths.
I use a tool called flatten-packages [1] and I usually do all of my npm work while visual studio is closed (and use short root paths as mousetraps suggested). I just flatten them after adding/updating/syncing packages. [1] https://www.npmjs.com/package/flatten-packages
That's worked well for me, too. The biggest problem with long file paths is the deeply nested dependencies, so flatten-packages handles it for me.
Re: Node.js Tools for Visual Studio
#48Earlier quoted context omitted.
> While we're at it, is the static analysis tools you built for this public? maybe this? http://nodejstools.codeplex.com/SourceControl/latest#Nodejs/...
Looks like it, yeah. Thanks!
Let us know if you have any questions! There's some _really cool_ stuff going on there, but it can be tough to wade through depending on your experience.
Re: Node.js Tools for Visual Studio
#49I remember a bunch of problems have been discussed earlier [1] concerning node.js on Windows, such as file-system path length limits and broken symlinks and lack of modules actually tested on Windows.
That was almost a year ago, so how do the things stand now?
Re: Node.js Tools for Visual Studio
#50Earlier quoted context omitted.
The people writing nodejs code are all using vim and unix No they aren't, that's just your perception because you are surrounded by those that are. AFAIK Windows Node developers are still a minority, but that doesn't mean they're not a sizable group of people. A lot of code is written in corporate environments in C# and Visual Studio - adding Node to that mix is a sensible bet on Microsoft's part.
Yeah I was being hyperbolic, but my point still stands. The LARGE majority of developers have accepted unix as their overlord, and that poses a huge problem to microsoft as they're a second thought. They're forced to try to fit new frameworks into their ecosystem, rather than on unix where developers expect it to run. I see it ultimately as damage control. With the overwhelming majority of developers on unix, you're…
What evidence do you have that the majority of developers are on Unix? Just web devs or all devs?
I doubt that it's true in either case. IT departments around the world employ programmers to make all sorts of business apps including internet/intranet web apps. Even some very small companies have custom apps to do business and the vast majority of businesses are using Windows.