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

71–80 of 127 posts

Re: Node.js Tools for Visual Studio

#71

Post by angersock »

mousetraps wrote: post #52
inglor wrote: post #20

Earlier quoted context omitted.

Any plans to make deployment of io.js easier to Azure websites? Also - any way we might get "break on exception" like with C#? Also - any plans to support debugging promises better?

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. :-\

Re: Node.js Tools for Visual Studio

#72

Post by Already__Taken »

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…

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

Re: Node.js Tools for Visual Studio

#73

Post by c0achmcguirk »

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.

Webstorm has CoffeeScript support too.

https://www.jetbrains.com/webstorm/help/coffeescript-support...

Re: Node.js Tools for Visual Studio

#74

Post by mynameisvlad »

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.

It just uses msysgit's ssh implementation.

Re: Node.js Tools for Visual Studio

#76

Post by rdtsc »

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…

> The 255 character path limit bug has been around for a long time and still unresolved/broken on Windows

I don't know, I was cussing out both node.js and Windows. "Let's put all the dependencies in subtree even if they repeat 20 times throughout or paths start wrapping around 3 times at the terminal".

Re: Node.js Tools for Visual Studio

#77

Post by int_19h »

nickysielicki wrote: post #15
untog wrote: post #12

Earlier 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 makes you think that Microsoft can't have a part of the Unix server slice, either? Have you seen e.g. this:

http://blogs.msdn.com/b/dotnet/archive/2015/02/03/coreclr-is...

(specifically the part that says "We will be adding Linux and Mac implementations of platform-specific components over the next few months.")

Or the part where ASP.NET vNext runs on Mono as the officially supported platform?

http://graemechristie.github.io/graemechristie/blog/2014/05/...

Re: Node.js Tools for Visual Studio

#78

Post by mousetraps »

Already__Taken wrote: post #72
mousetraps wrote: post #56

Earlier quoted context omitted.

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…

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

Re: Node.js Tools for Visual Studio

#79

Post by Hominem »

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.

Re: Node.js Tools for Visual Studio

#80

Post by mousetraps »

inglor wrote: post #20
mousetraps wrote: post #2

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

Any plans to make deployment of io.js easier to Azure websites? Also - any way we might get "break on exception" like with C#? Also - any plans to support debugging promises better?

Also re: io.js + Azure websites - looks like someone wrote a script to make it easier!

http://azure.microsoft.com/en-us/documentation/articles/web-...

Post reply on HN