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

121–127 of 127 posts

Re: Node.js Tools for Visual Studio

#121

Post by Already__Taken »

jyrkesh wrote: post #117
Already__Taken wrote: post #99

Earlier quoted context omitted.

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.

Any ideas for how a problem like that can be solved? User feedback on a closed-source project at massive scale?

I don't know. I guess you've just got to vet credentials? To avoid having a team to man the identity service perhaps;

If you need developer feedback maybe require the UX to be creating Pull requests describing the issue? Kind of like how pullup.io works?

Re: Node.js Tools for Visual Studio

#122

Post by Already__Taken »

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."?

Consider a fresh user installs nodejs, runs npm install , runs npm run start. Immediately they get a problem.

Doesn't look great for node and it shouldn't be their problem.

More like "We landed on the moon but sometimes the door won't open"

Re: Node.js Tools for Visual Studio

#123

Post by [deleted] »

jongalloway2 wrote: post #95
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

[deleted]

Re: Node.js Tools for Visual Studio

#124

Post by babby »

thearrow wrote: post #83
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.

You might want to check out sublime with the 'Better Coffeescript' and 'CoffeeComplete Plus' packages. I've been using it for a while and, while it's not perfect, it's the best I've found. https://github.com/aponxi/sublime-better-coffeescript https://github.com/justinmahar/SublimeCSAutocompletePlus

I agree, and it's close to usable but not quite. There are a few outstanding breaking issues on the repo that I wish someone who knew how it worked could fix, but the project looks abandoned.

I actually heavily modified sublime-better-coffeescript to support highlighting function-calls and I added proper CSJX support.

Been meaning to make a pull request; but these Sublime plugins are always so easily abandoned and under maintained that there's no point.

Re: Node.js Tools for Visual Studio

#125

Post by mousetraps »

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?

I posted this in the comments in the blog as well:

With regards to the technicalities of max_path itself... the issue is with the .NET file I/O API, which doesn't allow you to use \\?\ paths to work around it, and is too big for our team in particular to do much about. Here's a good article that might provide a little more context (it's a little old, and these "plans" they speak of never actually materialized.)

http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-path...

That said... we don't like it either, and we are still thinking about what we can do.

Re: Node.js Tools for Visual Studio

#126

Post by mousetraps »

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…

Hi bgarbiak,

You can use the "From Existing Node.js Code" project template to create a project from a folder, but the project file itself is a requirement for visual studio and also allows us to include helpful metadata (whether or not to analyze a directory, etc - most IDEs/text editors include a project file for this very purpose - they just hide it a little better). That said, at some point we'd like to change things up so that the project does feel more similar to the folder/file experience you might expect.

This is to change the project file to be more "transparent". https://nodejstools.codeplex.com/workitem/1855

There's also another issue to directly open a folder without requiring the user to take steps to create the solution/project. https://nodejstools.codeplex.com/workitem/209

Additionally, like rlp mentioned - make sure that "show all files" is turned on so that you can see everything in the folder, not just files you've defined as being a part of your project.

Hope that helps - let me know if you have any other questions.

Re: Node.js Tools for Visual Studio

#127

Post by ed_blackburn »

orand wrote: post #44
ed_blackburn wrote: post #41

Superb 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

There have been some intermittent Windows issues: https://github.com/iojs/io.js/issues/1005

Not Microsofts problem.

Post reply on HN