Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node.js Tools for Visual Studio

blogs.msdn.com

Post reply on HN
Print view View original

91–100 of 127 posts

Re: Node.js Tools for Visual Studio

#91

Post by gnoway »

mousetraps wrote: post #56
tdicola wrote: post #45

This 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-visua…

See comments on this thread re: max_path problems, workarounds, and how we help mitigate it in NTVS: https://news.ycombinator.com/item?id=9265694 Otherwise, yeah - we don't like it either... here's the not-closed uservoice request ;-) https://windows.uservoice.com/forums/265757-windows-feature-... EDIT: Re: fish: Indeed - we have some big fish to fry, but luckily msft is a big company that can fry multiple fish at a…

Why can't you (or node?) use the \\?\ syntax?

Re: Node.js Tools for Visual Studio

#92

Post by BinaryIdiot »

airtonix wrote: post #87
cabirum wrote: post #49

I 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? [1] https://news.ycombinator.com/item?id=7914566

windows not being a priority won't change, because windows as a deployment target is pretty much a joke. I mean... desktop environment on your application server ... lol? There's so much friction legality and culture wise to getting a windows server to spin up, get developers to use good practices, encourage automation and resusability...

> windows not being a priority won't change, because windows as a deployment target is pretty much a joke.

I take it you haven't done .Net development? It's incredibly easy though Docker and similar tech wasn't developed for Windows so some of that has lagged behind.

> I mean... desktop environment on your application server ... lol?

This is a pretty old way of thinking; it's simply another way of managing your application server. This really isn't a big deal anymore.

Re: Node.js Tools for Visual Studio

#93

Post by giancarlostoro »

Hominem wrote: post #79
nickysielicki wrote: post #9

How 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 actually use it. I'm not serious about web development though, I just do it for my job. I also use Python Tools for Visual Studio, but that is a different story.

From my personal experience, if I'm not on Windows I use PyCharm for my IDE, but when I am, and I have VS installed, Python Tools for Visual Studio is really what I consider, Microsoft's hidden secret for VS. It really is a powerful tool, it would not surprise me if NTVS is right up in the same level of quality. Really great tools. Otherwise I try to go for JetBrains.

Re: Node.js Tools for Visual Studio

#94

Post by axefrog »

MichaelGG wrote: post #16
mousetraps wrote: post #2

Dev here - happy to answer any questions you have :)

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.

If you use git, open a git bash window and do it from there. If you don't use git, install cygwin and do it from a cygwin bash window. Both are *nix-simulated shells and are not subject to the MAX_PATH limit. I do most of my command line work using Power Shell, but I always have a git bash terminal ready for npm, jspm and other similar path-length-affected tools.

Re: Node.js Tools for Visual Studio

#95

Post by jongalloway2 »

babby wrote: post #61

I was really excited about Visual Studio for a chance at Coffeescript intellisense, however I learned after the several gig download it wasn't supported. It seems there is basically no way to get proper autocomplete in any editor for CS, suggesting maybe I should just consider Babel for ES6/7 despite my massive love for CS and giant projects built in it.

Have you tried the (free) Web Essentials extension? It adds CoffeeScript support to Visual Studio, as well as a lot of other useful webdev features. http://vswebessentials.com/features/coffeescript

Re: Node.js Tools for Visual Studio

#96

Post by mousetraps »

angersock wrote: post #71
mousetraps wrote: post #52

Earlier quoted context omitted.

Break on exception? Done! http://nodejstools.codeplex.com/wikipage?title=Debugging#bre... We have SO MANY PLANS, so please upvote or request the ones you think are important :) https://nodejstools.codeplex.com/workitem/list/basic

I'd vote for the "Move to github", but (fittingly enough) I'm not going to create a codeplex account just for that purpose. :-\

Haha, fair enough. Then I suggest you follow @NT4VS on Twitter. We'll let you know when it happens. :-)

Re: Node.js Tools for Visual Studio

#97

Post by mousetraps »

azurelogic wrote: post #21
nickysielicki wrote: post #9

How 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…

It's super cool for people wanting to do node on Windows. I used the beta while doing a small side project at my last job, and they worked well for that project. My issue isn't necessarily azure and VS. It's the state of node on Windows. It's a second class citizen compared to the versions for posix compliant OSes. There are things that just don't work on Windows without installing VS, which is undesirable for deploy…

Fwiw we have remote debugging to any OS, so you can remote debug your app regardless of whether or not it's running on azure. We are striving to streamline this experience as much as possible, so any feedback or ideas you have on how to mitigate some of windows issues you've run into would be super helpful. :-)

Re: Node.js Tools for Visual Studio

#98

Post by teh_klev »

0xFFC wrote: post #53
radicalbyte wrote: post #51

Earlier quoted context omitted.

Just use cmder or conemu; then you'll have a great console and ssh :)

Thank you , last question , are they reliable ? ( I am installing them right now , but I think as you mention them , you can answer this question better ) Because I use SSH in my work and research all the time , I am kind of tired of putty and its bug's.

Check out MobaXterm [0], there's a free version but I ponied up for the Pro edition after just a week. I use it daily and its X support is really bloody good. I run PyCharm (and other stuff) on a CentOS machine but the GUI is on my Windows desktop.

[0]: http://mobaxterm.mobatek.net/

Re: Node.js Tools for Visual Studio

#99

Post by Already__Taken »

mousetraps wrote: post #78
Already__Taken wrote: post #72

Earlier quoted context omitted.

I thought connect was the official way to complain about MS things?

Technically... - connect is for filing bugs - uservoice is for "ideas and suggestions" How people use it, of course, is a completely different story... And then some teams (like us) have public issue trackers, which are the best approach if available because everything goes directly to the team: https://nodejstools.codeplex.com/workitem/list/basic

Ah I see. Yes I put a powershell bug/missing feature request on connect and looked through some other tickets. I don't envy whose reading that.

I think Ms is doomed to get people complaining about unrelated junk any time they open a platform up.

Re: Node.js Tools for Visual Studio

#100

Post by bgarbiak »

mousetraps wrote: post #2

Dev here - happy to answer any questions you have :)

Is there a simple way to use VS without the Solution files? Templates and Solutions are fine for creating a entirely new project, but if I have to work on someone's else code I'd prefer to have a basic "File Explorer" over Solution Explorer / Team Explorer. My attempts to create a new Solution file for an existing code ended with a new directory (or a couple of them) with a boilerplate code... Am I missing something obvious here?

Also, I've noticed that if I open a few files the IDE creates "Virtual Solution", but it's hard to tell which files are there, and which don't. For example: TypeScript files are, but no such luck with SASS.

P.S. And a CMD/Terminal in a panel (akin to the Output panel, but with an... well, input) - is that possible?

Post reply on HN