Live data from Hacker News

Node.js Tools for Visual Studio

hanselman.com

51–60 of 90 posts

Re: Node.js Tools for Visual Studio

#51

Seeing things like this gives me hope that one day Windows will be a first class os for web development. Now if I could just maximize the command prompt window....

windows is a first class os for web development. what is it lacking? i have coded in ruby, python, java and go for the web. also used different web servers including apache and tomcat.

For me the lack of many unix tools is a killer and cygwin doesn't cut it. Many build scripts assume a unixy environment and windows is flat-out not supported. Lack of a proper package manager also makes installing and configuring workstations a hassle.

Re: Node.js Tools for Visual Studio

#52
post #43
post #18

Earlier quoted context omitted.

i'll try to find out. top my head i know the azure node sdk is all node (obviously...), all the cross-plat commands/utils are node, skype, yammer, bing (?), ... all use node to various extents. some info: http://www.windowsazure.com/en-us/develop/nodejs/ https://github.com/WindowsAzure/azure-sdk-for-node https://github.com/WindowsAzure/azure-sdk-tools-xplat

TypeScript also uses node.

TypeScript uses npm as a package manager yes, but there is unfortunately no support for using Node within TypeScript yet on Visual Studio. There are definitions for node/express/etc, just cannot compile them directly in Visual Studio and also have debugging (unless the linked package in the OP has changed that).

Re: Node.js Tools for Visual Studio

#53
This is the kind of thing that makes me want to switch back to Windows.

I like VS since I've been using it to develop a C# app these last two months. I miss a lot of things because I'm too deep in CLI usage (like git...help me...), but had I had it when I tried to play with Ruby on Windows 7 three years ago and discovered the pain of the windows CLI, maybe I would've stayed there.

These Node.js tools are especially great. I spend a lot of time on CLI running my app, installing a module, watching my dev logs,... I couldn't ever imagine anyone using node.js on windows. Now I can and it looks great.

Re: Node.js Tools for Visual Studio

#55

Wow, for an alpha release that's pretty impressive. Node seems to be really taking off at MS...parts of Azure are built with it...some really large parts of Azure. It's awesome that they didn't screw with Node either to make it run on Chakra...

Do you have a reference for Azure internals being written in node.js? I'd love to read about it.

A colleague reverse engineered Azure Mobile services, written in Node, to find out how it works. He blogged about it here: http://weblogs.asp.net/soever/archive/2013/07/26/azure-mobil...

Re: Node.js Tools for Visual Studio

#56
post #43

Earlier quoted context omitted.

TypeScript also uses node.

TypeScript uses npm as a package manager yes, but there is unfortunately no support for using Node within TypeScript yet on Visual Studio. There are definitions for node/express/etc, just cannot compile them directly in Visual Studio and also have debugging (unless the linked package in the OP has changed that).

I should have been a bit more specific, Microsoft could have used any language to build the TypeScript compiler.

They took however the best solution by bootstraping it in JavaScript and using node for the process.

Just correct me if I am wrong.

Re: Node.js Tools for Visual Studio

#57
post #56

Earlier quoted context omitted.

TypeScript uses npm as a package manager yes, but there is unfortunately no support for using Node within TypeScript yet on Visual Studio. There are definitions for node/express/etc, just cannot compile them directly in Visual Studio and also have debugging (unless the linked package in the OP has changed that).

I should have been a bit more specific, Microsoft could have used any language to build the TypeScript compiler. They took however the best solution by bootstraping it in JavaScript and using node for the process. Just correct me if I am wrong.

Looks correct to me and makes the most sense to build the tools in the language TypeScript compiles to. On another note, it would appear they will be adding TypeScript support in the beta[1], which makes me very happy.

[1] https://news.ycombinator.com/item?id=6777360

Re: Node.js Tools for Visual Studio

#58
post #51

Earlier quoted context omitted.

windows is a first class os for web development. what is it lacking? i have coded in ruby, python, java and go for the web. also used different web servers including apache and tomcat.

For me the lack of many unix tools is a killer and cygwin doesn't cut it. Many build scripts assume a unixy environment and windows is flat-out not supported. Lack of a proper package manager also makes installing and configuring workstations a hassle.

It depends on what build scripts you are talking about.

We use Ant, Maven, MSBuild, Powershell, all without UNIX assumptions.

You can configure workstations via Active Directory.

Microsoft is not to blame if developers still insist in having .exe installers instead of adopting .msi packages.

Re: Node.js Tools for Visual Studio

#59
post #42

Earlier quoted context omitted.

Sounds reasonable :). Although I dread imagining a JavaScript equivalent of a "100+ project .NET solutions" built in spirit of "rapid development".

I do like dynamic languages for quick prototypes, but my experience on the scale of enterprise projects and their code quality, just increased my preference for static typing for production code.

TypeScript FTW.

https://nodejstools.codeplex.com/workitem/291

Re: Node.js Tools for Visual Studio

#60

This is the kind of thing that makes me want to switch back to Windows. I like VS since I've been using it to develop a C# app these last two months. I miss a lot of things because I'm too deep in CLI usage (like git...help me...), but had I had it when I tried to play with Ruby on Windows 7 three years ago and discovered the pain of the windows CLI, maybe I would've stayed there. These Node.js tools are especially g…

Let me guess, you used plain cmd instead of PowerShell.
Post reply on HN