Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Debugging a total failure of a Hello World node.js demo!

28 minutes, 53 seconds


Right click “Save as…”

Scott messes up a node.js demo then spends the next 30 minutes debugging it, learning more about Azure in the process!


Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • JeroenHJeroenH

    I think the problem actually wasn't the missing server.js. If you look carefully, the last commit deleted *2* files and also changed one. I'm would guess there lies the key...

  • Windows Azure Web Sites adds a web.config to your deployment which wires up iisnode to look for server.js. Your express package was saying that your application start file was app.js

    another way to fix this would be to modify the web.config to point to app.js, this way if server.js was still required for your application to run iisnode would use app.js as your application entry point and server.js could still be referenced from your code.

Remove this comment

Remove this thread


Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.