Node.js Tools for Visual Studio
blogs.msdn.com
Node.js Tools for Visual Studio
1–10 of 127 posts
Re: Node.js Tools for Visual Studio
#2Re: Node.js Tools for Visual Studio
#3Dev here - happy to answer any questions you have :)
In the meanwhile, I noticed that you support intellisense. What are the limitations to this? What patterns will get correctly picked up? I assume prototypal inheritance will work fine (of course), but will any of the BaseClass.extend()-style inheritance mechanisms that some frameworks seem to favour (e.g. Backbone) work?
While we're at it, is the static analysis tools you built for this public? I'd love to have a look at them.
Re: Node.js Tools for Visual Studio
#4Re: Node.js Tools for Visual Studio
#5Dev here - happy to answer any questions you have :)
Love Azure, but had a hard time getting my NodeJS stuff up to Azure without some major issues.
Re: Node.js Tools for Visual Studio
#6Dev here - happy to answer any questions you have :)
Great work, looks very nice. Will give it a whirl when I get home. In the meanwhile, I noticed that you support intellisense. What are the limitations to this? What patterns will get correctly picked up? I assume prototypal inheritance will work fine (of course), but will any of the BaseClass.extend()-style inheritance mechanisms that some frameworks seem to favour (e.g. Backbone) work? While we're at it, is the stat…
maybe this?
http://nodejstools.codeplex.com/SourceControl/latest#Nodejs/...
Re: Node.js Tools for Visual Studio
#7Dev here - happy to answer any questions you have :)
Is this going to make it easier to deploy NodeJs apps to Azure then? Love Azure, but had a hard time getting my NodeJS stuff up to Azure without some major issues.
Re: Node.js Tools for Visual Studio
#8Dev here - happy to answer any questions you have :)
Is this going to make it easier to deploy NodeJs apps to Azure then? Love Azure, but had a hard time getting my NodeJS stuff up to Azure without some major issues.
Windows is not a priority for most node.js devs, so unless you're doing something pretty simple/mainstream, you're likely to run into trouble.
Re: Node.js Tools for Visual Studio
#9I 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 framework certainly will be on unix first. MS is now in this perpetual state of trying to keep up, and I just can't imagine why anyone serious about web programming wouldn't be on *nix.
Re: Node.js Tools for Visual Studio
#10Earlier quoted context omitted.
Is this going to make it easier to deploy NodeJs apps to Azure then? Love Azure, but had a hard time getting my NodeJS stuff up to Azure without some major issues.
I gave up on deploying my node.js app to Azure after finding that several modules I was using were simply not possible to run on Windows. Wasn't worth the trouble to refactor and avoid these dependencies. Windows is not a priority for most node.js devs, so unless you're doing something pretty simple/mainstream, you're likely to run into trouble.