ASP.NET Cloud Hosting developer checklist

Categories Web HostingScriptingASP.NET Tags cloud hosting

This article is for customers using our Cloud Hosting Windows server environment.

If you are a web developer or a designer who wants to run a ASP.NET application in our Cloud Hosting server environment, use the below as a checklist to ensure you have configured your application accurately. All of the instructions below involve your web.config file. We are merely configuring your application to work with Clustered shared hosting.

Make sure you can see detailed error messages

By default, your application will hide errors and merely throw a "500 Internal Server Error" message if it can't do something. If you can't see the true server errors for your application it's impossible to debug your code. To save yourself the frustration, start any development by enabling Detailed errors in your web.config. Edit web.config to include the following code:

<httpErrors errorMode="Detailed"/>

Make sure any web requests are done via a Proxy

If your application needs to connect to any third party or even local server hostnames via HTTP, you will need to use our proxy server. Simply add the following code in your web.config once, somewhere above any third party connection:

<proxy usesystemdefault = "false" proxyaddress="" bypassonlocal="true" />

Save your session data to Session State

Session data is externalised in clustered environments due to the nature of the task at hand -- saving session data on the webserver used for the request means potential loss of data as another request is made via a different node inside the cluster. We supply a Session State server to save session data to. The code to add to your web.config is:

<sessionState mode="StateServer" stateConnectionString=""/>

For full details on Session State, please see Session Handling on IIS.

Create a MachineKey for your application

MachineKey assists in validating session data. View the full details on creating a MachineKey on our Creating a Machine Key for ASP.NET applications support article.

Add a Web Application directory to use it's own Application Pool

If you have more than one application that you'd like to run on your hosting account, you can add a new Web Application directory using the Console. See the article on Adding a Web Application Directory on IIS for details on how to add it.

Make use of preinstalled modules and frameworks

We have installed the following modules on our Windows cluster to assist customers with the most common of website functions. Click the links below for full support information on the usage of those components - all of these link to the vendor documentation:

Something is not working and the error is not making sense, who do I ask to help me?

You can contact our support centre. While we don't supply coding/development support, we can make sense of an error message and point you in the right direction. From our experience, in the majority of cases where customers have come across difficulties with their .NET applications, one of the above web.config updates in this article was not observed.

Rate this article