Debugging Node.js applications for Windows Azure
Posted
by cibrax
on ASP.net Weblogs
See other posts from ASP.net Weblogs
or by cibrax
Published on Thu, 22 Mar 2012 14:08:24 GMT
Indexed on
2012/03/22
17:31 UTC
Read the original article
Hit count: 342
In case you are developing a new web application with Node.js for Windows Azure, you might notice there is no easy way to debug the application unless you are developing in an integrated IDE like Cloud9. For those that develop applications locally using a text editor (or WebMatrix) and Windows Azure Powershell for Node.js, it requires some steps not documented anywhere for the moment.
I spent a few hours on this the other day I practically got nowhere until I received some help from Tomek and the rest of them. The IISNode version that currently ships with the Windows Azure for Node.js SDK does not support debugging by default, so you need to install the IISNode full version available in the github repository.
Once you have installed the full version, you need to enable debugging for the web application by modifying the web.config file
<iisnode
debuggingEnabled="true"
loggingEnabled="true"
devErrorsEnabled="true"
/>
The xml above needs to be inserted within the existing “<system.webServer/>” section.
The last step is to open a WebKit browser (e.g. Chrome) and navigate to the URL where your application is hosted but adding the segment “/debug” to the end. The full URL to the node.js application must be used, for example, http://localhost:81/myserver.js/debug
That should open a new instance of Node inspector on the browser, so you can debug the application from there.
Enjoy!!
© ASP.net Weblogs or respective owner