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

101–110 of 127 posts

Re: Node.js Tools for Visual Studio

#101

Post by yummybear »

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…

Isn't this a bit like saying "It's great we landed on the moon and all, but shouldn't we concentrate on stuff like curing cancer."?

Re: Node.js Tools for Visual Studio

#102

Post by boldrikboldrik »

AdeptusAquinas wrote: post #86
thebouv wrote: post #82

Gotta hand it to Microsoft. Behind the times on web dev for so long, now busting out open source left and right, teaming up on Angular with Google, jumping on with nodejs, modernizing their tools, "gently" pushing locked in MS web devs out of the darkness of that Web Forms madness into the light of real web development. I've always been a LAMP stack dev but they have at least caught my attention as of late.

>"gently" pushing locked in MS web devs out of the darkness of that Web Forms madness Minor nitpick on your otherwise positive comment, we have been using ASP.NET MVC for almost ten years now (ok eight). Webforms have long been a thing of the past, at least in the circles most devs I know move in.

I think it's think of past on new projects, but old and intranet project still use Web Forms. For me it's (unluckily) still most of my work.

Re: Node.js Tools for Visual Studio

#103

Post by mousetraps »

scubadude wrote: post #64
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…

Ultimately, MS' business in web development is tied to selling an IDE and Azure. Both have had to change to incorporate the tools people are using (JavaScript), not just the tools MS control (C#/.NET). I agree, the "Embrace, extend and extinguish" philosophy has apparently been replaced with "Embrace and hope to stay relevant". I think they are doing a good job at handling that change. I don't personally want to be c…

I can't speak for other teams, but re: NTVS... we definitely dont want to force abstractions upon you. For instance, with the npm integration, we provide UI where it makes sense (exploring/managing your packages, searching for packages), but you can drop into the cmd line or .npm command in the interactive window anytime you please. Think of it as semantic zoom - allowing you the flexibility to traverse the levels of abstraction when it makes sense. Are we 100% there yet? No. But I consider that to be the ideal experience, and we're definitely trending closer to that vision.

Thoughts? I'm especially curious to hear how you think we can improve the existing experience so that it caters better to your workflow. What are some of the abstractions that get in your way?

Re: Node.js Tools for Visual Studio

#104

Post by Drakim »

yummybear wrote: post #101
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…

Isn't this a bit like saying "It's great we landed on the moon and all, but shouldn't we concentrate on stuff like curing cancer."?

It's more a bit like saying "It's great we landed on the moon and all, but shouldn't we concentrate on making spaceships safe first?"

Re: Node.js Tools for Visual Studio

#105

Post by rlp »

bgarbiak wrote: post #100
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…

Try clicking the Show All Files button at the top of the solution explorer. It will show everything by folder, which I think is what you're looking for.

Re: Node.js Tools for Visual Studio

#106

Post by ygra »

xenadu02 wrote: post #58
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…

MAX_PATH is the gift that keeps on giving . Thanks to Microsoft's fanatical dedication to compatibility I don't see how it will ever get fixed. I think they could take a lesson from Apple here and have DLLS/EXEs contain SDK versions against which they are built, then mandate that Windows 10 apps must support a larger MAX_PATH. Of course if they were into learning lessons, they'd have done fat binaries so a single ins…

MAX_PATH is a #define, so it just gets literally substituted when compiling, there is no need for people copying it. After compilation it effectively is a hard-coded constant, indistinguishable from literally writing 260 (it's not 255).

Re: Node.js Tools for Visual Studio

#107

Post by michaelx386 »

gnoway wrote: post #91
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…

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

For anyone else like me who didn't know about this \\?\ syntax:

http://stackoverflow.com/questions/21194530/what-does-mean-w...

https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...

Re: Node.js Tools for Visual Studio

#108

Post by blumkvist »

pistle wrote: post #90
jeswin wrote: post #84

Earlier quoted context omitted.

> Gotta hand it to Microsoft. Behind the times on web dev for so long, now busting out open source left and right, .... Open Source is not just about opening up some source code, it is also about how you act in the larger interests of the community. Just earlier this month, Microsoft sued Kyocera over patents on Android. Microsoft has sued every Android phone maker so far, and have forced some of them to make Windows…

Forest, meet trees. MS is a very large company with divergent groups given KPI's that turn into seemingly contradictory actions. It's the Kabuki theater of patent suing in order to eventually end up at a table finding a way to forge ahead "together." It's something the large IP players have all been doing on the long tail of the IP consolidation wars. IP royalty harvesting is separate enough from the open source effo…

Posts like these are the reason why I visit HN.

Re: Node.js Tools for Visual Studio

#109

Post by pionar »

boldrikboldrik wrote: post #102
AdeptusAquinas wrote: post #86

Earlier quoted context omitted.

>"gently" pushing locked in MS web devs out of the darkness of that Web Forms madness Minor nitpick on your otherwise positive comment, we have been using ASP.NET MVC for almost ten years now (ok eight). Webforms have long been a thing of the past, at least in the circles most devs I know move in.

I think it's think of past on new projects, but old and intranet project still use Web Forms. For me it's (unluckily) still most of my work.

I work on a 12 year old application that's still current, and we're just now making the transition from web forms to MVC in that application. It's so nice that MSFT has a big eye toward backwards compatibility, allowing web forms and MVC in the same project.

Re: Node.js Tools for Visual Studio

#110

Post by pionar »

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.

WebEssentials extension for this. I use it with CoffeeScript and LESS.
Post reply on HN