You probably need to change the startup script in such a way that it installs the node.exe under a new process in IIS, using the startup script I assume you should be able to have node.exe running on the same box as your web role.
I am not very sure what's the "node.js connections" mean. Do you want to use Node.js as the HttpHandler in your application? perhaps you can create this HttpHandler by Node.js and use HttpWebRequest to connect the handler via Web Form or MVC.
Just like a normal HttpHandler that writen by C# code.
What I want is a thumbs up or thumbs down on whether a single web role in Azure will allow me to have an ASP.NET Session object and will allow me to update the client page through interactions with the same web role using node.js on the server and client.
Thus the Web Role would be running ASP.NET code that was written in C# and Node.js and I could interact with this single Web role running node.js on the server as well as normal ASP.NET. This would mean I could access the server via AJAX posts and node.js.
If you ask me anything deeper, I don't think you understand the question. Asked another way, in a single web role can I have C#/CLR code running and also be running node.js?
Well, I think you don't really understand what the asp.net and the node.js . Node.js just make js a new language extreamly like the c sharp language, and they both can work well on the dotNet freamwork, but you have to install the node.js on your server.
something wrong, welcome for telling me.Thanks.