31–40 of 70 posts
Until they can address the problem with building certain NPM modules on windows (ie `node-gyp` related ones), this is a bit of a non-starter. Sadly the only reason I keep my windows based desktop around these days is PC gaming is still very much windows based.
Now on this Node.JS IDE, it actually makes me want to use Node.js because it's on Visual Studio, however, I'm also open to alternative IDE.
My favorite is Jetbrain's IDE products, I use webstorm and phpstorm, and pycharms. I love them all, would be nice if they had one for Node.js, as I'm not sure if webstorm has extensive support for it.
http://nodejstools.codeplex.com/releases/view/104141
https://www.youtube.com/watch?v=ZAroJmb6XY4
It was in the original title, but has been edited out.
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...
Their new OS in a sense is Azure, they want developers of all platforms to run on their cloud. All of these tools have an easy tie to Azure which isn't bad, but the lock-in is happening farther up at the service level now. Web developers are huge in that area.
As with most Microsoft stuff, you get a great fully integrated story if you use their whole stack, but if you want to swap one one piece it falls apart a little. My clients have compliance issues that make cloud providers hard to use so it's disappointing that I can't really use all this coon new stuff.
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 feature is this Beta are TypeScript integration, Remote debugging (inc. linux), Edit&Continue (no server restart), free edition (NTVS + VS Express), etc. and numerous bug fixes.
To address a few comments regarding strategy - most are correct, though some are over thinking it a bit :). The project was proposed & started by the PTVS (python) folks, and mgmt was rather lukewarm about it. It was definitely not part of some uber P1 strategy. I wish it was. However, since then it's gained some momentum thanks to the community and it's become important enough that Scott Guthrie mentioned it in his keynote, and Soma (SVP for developer division) just blogged about it.
a few new videos (pls excuse the production, we do our own videos...)
new npm UI (community contributed) https://www.youtube.com/watch?v=AwSzxFY5CMI
twitter sentiment app -- https://youtu.be/9tf6HmG9VAA
remote debugging https://www.youtube.com/watch?v=ZAroJmb6XY4
It's better late than never. It's just easier to say 'I quit' because it's likely none of Node.js developers will switch to using Visual Studio rather than give it a try. Though I probably will never use Visual Studio for writing my Node.js project, kudos for MS not being the old MS. So what's next for MS? I think they are getting the direction right for opening up for external MS product users, and now it's time to…
I think msft building this kind of tooling around exciting tech like node gives node more credibility in a big enterprise type of shop...will only be a good thing for node,
I tried the alpha a few months back, and found it to understandably be lacking, My biggest frustration with it was trying to profile the performance of a complex piece of code with a number of callbacks and such. NTVS would only look at the first iteration, and not tell me anything useful (at the time I was tracing a memory leak). There were a few other inconveniences which I noticed that issues were raised for, hope…
I'd sell a good friend of mine if I could debug my node extension native code and javascript server code from the same IDE.
Until they can address the problem with building certain NPM modules on windows (ie `node-gyp` related ones), this is a bit of a non-starter. Sadly the only reason I keep my windows based desktop around these days is PC gaming is still very much windows based.
Until they can address the problem with building certain NPM modules on windows (ie `node-gyp` related ones), this is a bit of a non-starter. Sadly the only reason I keep my windows based desktop around these days is PC gaming is still very much windows based.
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?
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.