Live data from Hacker News

Node.js Tools for Visual Studio

nodejstools.codeplex.com

41–50 of 70 posts

Re: Node.js Tools for Visual Studio

#41
post #35

(group lead here) Thanks GravityWell for posting. We just got done giving a talk on NTVS & PTVS at Build in SF. The reception was great (given this is a primarily .net conference). I did an informal poll of the audience (180 or so), asking whether they were planning on deploying node/python in their enterprise . The response was around 75-85% Yes to both, which was somewhat higher that I had expected. The cool new fe…

It is great that the installation works with Express. Much preferable to the approach taken by the Python Tools for VS requiring a separate installation of the bare VS shell. They say they can't enable installation of PTVS on Express because Express doesn't support extensions. I guess you aren't doing NTVS as an extension. Any hope for getting PTVS to install on Express using whatever method you are using?

Re: Node.js Tools for Visual Studio

#42

Earlier quoted context omitted.

I keep hearing this meme but I use node on Windows and don't have any issues with this. You have to have Visual Studio and Python installed, but most of us have that anyway. Which node modules are problem children?

We had a lot of issues with sqlite. What version of VS did you need? Some of the information on getting gyp working was like VS2008 SP1, plus the Win7.1 SDK. If this is no longer true, I'll give it a whirl.

I use VS2013 with it and it works great.

Re: Node.js Tools for Visual Studio

#43
post #41
post #35

(group lead here) Thanks GravityWell for posting. We just got done giving a talk on NTVS & PTVS at Build in SF. The reception was great (given this is a primarily .net conference). I did an informal poll of the audience (180 or so), asking whether they were planning on deploying node/python in their enterprise . The response was around 75-85% Yes to both, which was somewhat higher that I had expected. The cool new fe…

It is great that the installation works with Express. Much preferable to the approach taken by the Python Tools for VS requiring a separate installation of the bare VS shell. They say they can't enable installation of PTVS on Express because Express doesn't support extensions. I guess you aren't doing NTVS as an extension. Any hope for getting PTVS to install on Express using whatever method you are using?

Thx. Happy to report that the restriction is gone. In fact you'll be able to install PTVS in web and desktop express both! Release coming soon.

Re: Node.js Tools for Visual Studio

#44
post #28
post #18

Earlier quoted context omitted.

According to this the demand was highest in 2005. :)

Sorry, still true: http://www.google.com/trends/explore#q=nodejs%20mac%2C%20nod...

That's a search trend. It includes people searching for help. I'm not surprised Windows leads it for Node, it's a pain to work with most *nix software (especially that which doesn't have a point and click interface) on Windows.

Re: Node.js Tools for Visual Studio

#45
post #4

Does anyone else get the impression that MS shifted a lot of its attention to web developers? There is an incredible amount of web technologies and dev tools coming from ms that are being presented at Build 2014. In fact so many that I'm having a hard time keeping up...

Where does it say that this was made by MS?

Re: Node.js Tools for Visual Studio

#46
post #35

(group lead here) Thanks GravityWell for posting. We just got done giving a talk on NTVS & PTVS at Build in SF. The reception was great (given this is a primarily .net conference). I did an informal poll of the audience (180 or so), asking whether they were planning on deploying node/python in their enterprise . The response was around 75-85% Yes to both, which was somewhat higher that I had expected. The cool new fe…

Please use Typescript by default.

Re: Node.js Tools for Visual Studio

#47
post #17

Without going too far off-topic, does anyone know anything about a SQL Server driver for Node.js? There was this, but it hasn't been updated in a while. https://github.com/Azure/node-sqlserver

I find the tedious npm module works a bit better, and cross platform for connecting to MS-SQL, it has some rough edges, but was at least more consistent for me. The MS client didn't work as well for me early on. It's worth noting my usage has been pretty limited.

Re: Node.js Tools for Visual Studio

#48
post #35

(group lead here) Thanks GravityWell for posting. We just got done giving a talk on NTVS & PTVS at Build in SF. The reception was great (given this is a primarily .net conference). I did an informal poll of the audience (180 or so), asking whether they were planning on deploying node/python in their enterprise . The response was around 75-85% Yes to both, which was somewhat higher that I had expected. The cool new fe…

Do you guys do any automated testing of node.js apps on windows hosts via vagrant? The vagrant-windows and winrm gems are woefully out of date and broken on vagrant 1.5.1, so I was wondering how you guys handle testing node.js apps running on windows.

Re: Node.js Tools for Visual Studio

#49

Earlier quoted context omitted.

We had a lot of issues with sqlite. What version of VS did you need? Some of the information on getting gyp working was like VS2008 SP1, plus the Win7.1 SDK. If this is no longer true, I'll give it a whirl.

I use VS2013 with it and it works great.

EE?

Re: Node.js Tools for Visual Studio

#50
post #4

Does anyone else get the impression that MS shifted a lot of its attention to web developers? There is an incredible amount of web technologies and dev tools coming from ms that are being presented at Build 2014. In fact so many that I'm having a hard time keeping up...

This is an industry shift in my opinion. People are sick of writing the same app three times and it wouldn't surprise me to see many more hybrid apps in the next year.
Post reply on HN