Ntvs: Tools to turn Visual Studio into node. js IDE

Ntvs (node. js Tools for Visual Studio) runs on VS2012 or VS2013. Some of the node. JS enthusiasts have shifted from PTVs (Python tools for Visual Studio) and started to do some node tools for vs. The PTVs team also worked on node. JS integration, so they focused on Ntvs making it a community project. Ntvs was developed by the same team that brought you PTVs, and Bart Read from Red Gate (he developed the node Packaged modules graphical user interface), helped by Clickberry Dmitry from Tretyakov, They have done some debugging with functional repair.

Ntvs from the beginning is open source, and from the beginning to adopt the contribution. It supports editing, IntelliSense, Analytics, NPM (Node module encapsulation), Local and remote debugging (when the server is running on Windows/macos/linux), and publishing to azure websites and cloud services.

How they do this is pretty amazing, so I suggest you download and try it, because some of these things (even if it's only the original version here) are very, very smart.

Ntvs combines the V8 Analytics app with the reporting features of Visual Studio to tell you where your program consumes its time.

Tip: See above file| is the dialog box for New project? Visual Studio follows the development language organization type, so node. JS is under the JavaScript classification. But you also notice the classification of iOS and android,typescript,vb,f# in the python,django,c# category in Visual Studio.

One of the things that impresses me is that when they integrate node. js into Visual Studio, there is no new or redo functionality that has been perfected in Visual Studio. This is node, running in Node.exe, using the V8 debugger, using the V8 parser because that's what people are using. However, for example, Ntvs can get output from the V8 parser and display the results using the Visual Stuido Analysis Report Tool. There's no need to start over, just use the right tools to get the job done.

Use Ntvs to complete the Ghost blog engine

Let's take a look at an example.

L Download and install node from http://nodejs.org.

L Next, download Ghost from https://ghost.org/download/and unzip it to a place.

L Download and install Ntvs in the Visual Studio root directory from install node for Visual Studio.

L options available. Install http://vswebessentials.com because it makes network development in VS easier to display.

Starting with Visual Studio, the order is file | New Project, click JavaScript, and then select "From Existing node. js code".

Point the Ntvs to your ghost directory.

Then set up node. js to start the file as Index.js, click Next, save the project file and finish.

At this point, you've set up Ghost in vs.

Remember: Since I got the page features I also get a good benefit-screen markdown editor.

From here, click on F5 to debug, or Ctrl-f5 to start directly. Note, of course, that the node path is displayed in the Project Properties window in the lower right corner, and the port has a start file. You can certainly modify them.

Here I run ghost locally. You can see the path of node, ghost.js file and my browser.

You will get hints of implementation and help from the method signature.

Debugging

The Ntvs contains full debugging support for the node application. This includes stepwise debugging, breakpoint debugging, "Exception break", as well as local Variables window, Observation window, instant window and Call Stack tool window.

You can handle exceptions like services in other languages. See the following dialog box, node. JS Exceptions and other exceptions are listed in the classification that is processed with the unhandled code.

With the node V8 debugger, debugging always runs the way it usually does. Unless Visual Studio connects the debugger with a different socket (remember, you can even run debug node. js remotely on a Linux or Mac system like this) and will V8 how to do debug escape for Visual Studio how to do debugging. This feeling is seamlessly linked.

With this, you can see that Node.exe has been debugged and I'm running ghost. You can see my call stack and local variables in the observation window. I can view the variables, step through the debugging and do whatever you want to do when you debug a Web application.

Npmvisual STUDIO

The experience of using NPM is also pretty cool. Ntvs always monitors the file system, so running NPM as a command-line or node-direct window is a much more popular way to see changes in Visual Studio.

You can also use the NPM Package Management dialog box and search the library for a graphical installation package. It depends on you.

This is a package in the installation ...

The physical node module and the operation of these modules are purely code-only ... VS doesn't involve or care about it. However, Visual Studio's Solution Explorer (Solution Explorer) also renders a physical view in logical view.

Hint: I like this very much. I think it has potential and I prefer it. NET references are also handled as such. The physical and logical dependency tree shows the NuGet package. This helps me to better understand the project.

There's more. There is a REPL interactive window, you can use the same Publishing Wizard as other network projects to publish network Engineering with ASP. You can also publish your node. js application directly to Azure, using Git or Visual Studio.

You can also remotely debug a node instance on another machine by introducing a remote debugging agent to start node.

1	Node. EXE remotedebug. JS -machineport 5860 script. JS

As mentioned, you can debug remotely on Visual Studio and node running on any server operating system.

Summarize

I am personally delighted that Visual Studio is turning into a full component language and development environment factory (for me, in the short term).

Ntvs is fully open source under Apache license and they welcome contributions and bug reports. This is the original version but it's great. Go ahead and use it. Bless all the people involved!

Ntvs: Tools for turning Visual Studio into node. js IDE