iisnode

I am using a Rewrite rule in my web.config file for a node app running under issnode to point to my server.js file. myapp/* points to server.js. <rule name="myapp" enabled="true"> <match url="myapp/*" /> <action type="Rewrite" url="server.js" /> </rule> This has been working great www.mywebsite.com/myapp/ would load a run my app. What I wanted was to have a redirect from the root of the website so www.mywebsite.com/ would run my app. So I changed my web.config file <rule name="myapp" enabled="true"> <match url="/*" /> <action type="Rewrite" url="server.js" /> </rule> So this is running the

I can't get msnodesql to install. Originally I tried npm install node-sqlserver ... and this warns that it has been superceded by msnodesql. I successfully installed Node.js, iisnode and I see the sample Hello.js being served up (yayee, wonderful), so at least node and iisnode are working. I installed the prereq's: Node.js - use the latest version if possible, but it has been tested on node 0.6.10 and later node-gyp - latest version installed globally (npm install -g node-gyp) python 2.7.x - for node-gyp (make sure it is in the path) Visual C++ 2010 - the Express edition is freely available

Info: I am very new to node.JS! I have written a sample server that can listen to http requests on port XXXX. When I run this server from commandline (Windows) it seems to work well. It responds to the requests made to localhost:XXXX when opened in a browser. Question: Is this how this is supposed to work? For the node server to run, should there always be a CMD prompt open for the server to listen to requests? Can I not do "something" with IISNode? I understand that if I make a request to a JS files, which is noted in IISNode as a Node.JS file and that NODE should be handling it; then I will

I am using Windows Azure Websites to host a node.js application. So far everything is great except for my custom errors. In my node app I have an error handler that renders a custom 404 and custom 500 error page just fine on my local machine. However, as soon as I publish to azure it overrides the response when I set the statusCode to anything except 200. If I don't pass the 500 or 404 statusCode to the response then this does not happen, but I do want the status codes to make it to the browser. Locally I get my custom error page just fine: However, on azure websites it only returns a single

I have the following setup in IIS: Default Web Site (www.foo.com) hosting standard html site Web Application underneath Default Web Site (www.foo.com/bar) running IIS Node Node project is utilizing express I cannot for the life of me get this thing configure correctly so when I hit the web application is serves up the node application correctly. I think my problem lies in the web.config. Can anybody help me write a correct web.config to get this working correctly? The current version of my config will server me a node response that says it cannot get the resource at whatever url I type. Here