Knowledge Base
Preparing your .ASP/.NET website for CSN's upcoming Cloud Sites maintenance.

The purpose of this article is to assist you in preparing your ASP/.NET website(s) for our upcoming Cloud Sites maintenance.*

What changes are being introduced during this maintenance?
We will be standardizing on the MySQL .net connector 5.2.5
We will be installing .NET 3.5 Service Pack 1
We will remove support for Visual J# on our clusters in the SAT data center.

NOTE: These changes support Microsoft's scheduled end-of-life date for .Net 3.5 and Visual J sharp of July 12th, 2011.

NOTE: For a list of known issues and breaking changes for ASP/.NET within .NET 3.5 Service Pack 1, please click here.

What does this maintenance mean to you?
While we don't expect any downtime or disruption, we wanted to reach out to you to provide adequate notice to allow you to make any necessary changes that may be needed due to the upgrade of .Net Service Pack 1 or the removal of Visual J# support.

When will the maintenances take place?
NOTE: The "/" within the table below indicates no changes will be made on the specified cluster. The clusters in the chart with a white background have almost completed updating/maintenance.

You can check to see what cluster your website(s) are on by viewing the Staging URL.

How can I prepare for this change?
You can test the upcoming changes by simply creating (provisioning) a new "testing URL". To have a new testing url created, please contact CSN at 661.269.2398, or email to There is no additional hosting charge for a testing url. The testing url will be a subdomain and constructed as follows: http://www.test01.[yourdomainnamehere]/. If you have more than one site which will be updating, and would like to do a test url for each, a test url will be set-up for each site you would like to test and back-up.

Once you have setup your "testing URL[s]", you will then want to move a copy of your current site to the testing domain. You can do this by copying your website from the live site, and then loading the copy to the new, testing domain.

NOTE: If you have any databases, you will also want to make a backup of the database, and then import this into a new database on your testing domain.

Here is an article that will show you how to use MyLittleAdmin to create a backup and perform a restore of your MSSQL database(s).

You can also use FTP to move a copy of your website to the testing domain. Or, you can simply back-up your site[s] on your own desktop and/or server.

The finish line.
Once you have created your new testing domain and moved a copy of your website(s) over to it, you can now view your website on clusters that are already using the MYSQL .net connector 5.2.5, running .NET 3.5 Service Pack 1, and no longer carry support for Visual J#. At this time, you may need to make modifications to your site to ensure its functionality.

A few additional things to consider:
You might need to make some modifications to how your default documents are handled in your web.config. We have an article that will show you how to properly set your default document that can be viewed here.

You might need to modify how your MIME types are defined in your web.config. We have an article that will assist you with properly defining your MIME types here.


* takes no responsibility whatsoever for any files, code, content, database back-ups that are not made and/or are not made/done correctly. The information included on this knowledgebase page is usual and customary DB back-up procedures, but may not be complete. It is the client's responsibility to ensure that their site material is correctly backed-up. If a client prefers to make other arrangements or methods for backing up site material, it is at their sole discretion. always recommends that client back-up their entire site on a regular schedule.


Copyright 2011, a subsidiary of Group One Communications, Inc., All rights reserved worldwide.
Please review our Terms, Conditions, Policies, Procedures, Terms of Use and Service.