-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How does NTVS compare with Visual Studio Code? #86
Comments
Good question. Right now it's tough to provide much guidance because it's only day 2, and we're genuinely interested in listening to user feedback so that we can learn how to best improve the overall Node.js dev experience going forward. The advantages of NTVS are - as you mentioned - the feature-set and maturity of the product. From a quick glance... with VS, you're going to get more advanced debugging (conditionals, remote debugging, etc), unit testing, cloud/deployment integration, more semantically-correct IntelliSense for JavaScript using the NTVS static analysis engine (I believe VSCode will just show you all identifiers unless you import a tsd file), profiling, all the awesome VS extensions already available (e.g. web essentials, package intellisense, task runner explorer, cool IoT stuff, etc.), starter project templates, npm integration, interactive window... On the other hand, VSCode is cross-platform, super lightweight, has a file/folder-based project system, code actions (lightbulbs), more seamless switching between client-side and server-side editing experiences, and can potentially evolve more quickly since it's being built from the ground up and isn't limited to long-established VS-isms. So ultimately... if VSCode works for you, that's awesome! If NTVS works for you, also awesome! If you want to use both, but for different purposes... you get where I'm going. 😃 I personally suggest is playing around with VSCode now, and if you like something in VSCode that's not in NTVS or vice versa, please please please let us know. Any feedback is much appreciated 😃 |
Thanks! A great answer. From some of the comments during /build it seems Code is focussed more on the tight edit/debug loop though you can add commands to it. VS Enterprise and to a lesser extent Pro address the big picture. VS is great and now there is community it is usable by open source projects. I've not yet decided if VSCode + command line build is the way to good for me with VS for the tough debugs etc. I think you are correct about intellisense support - they talked about levels of support for different languages. I'm not ready for typescript just yet. :) PS Am going to try Vorlon too for client debug Will certainly let you know of any features requests etc Have just updated to VS 2015 RC so will try NTVS 1.1 beta |
This recording of the #build2015 presentation explains more. It seems you get a lot by using the TS files in JS |
Fix microsoft#86 startup file setting breaks debugger - rename "Node.exe arguments" -> "Node.exe options" to be consistent with node --help - rearrange arguments so that they are in the order they are supposed to be appended to one another - create a new "script (startup file)" property so that it is visible what arguments are getting passed to node from the General properties page, and doesn't block right clicking the file and setting as startup file or modifying it from file properties. Fix microsoft#65 Enable "Set as Node.js Startup File" context menu item for all filetypes - add a special case for when there is no exension specified, as is the case in the default express 4 template.
Watching Build I saw https://code.visualstudio.com/ launched and wondered what the advantages of each is? Certainly VS + NTVS offers a lot more functionality. But what if just deving a node based HTML app / website?
The text was updated successfully, but these errors were encountered: