This document describes two approaches to upgrading CCNet: a quick upgrade process (optimistic) and a slower, safer upgrade process that allows for quickly rolling back to the earlier install if required (pessimistic).

Optimistic Approach:

1. Stop the CCNet server (either by closing the console window or stopping CCService)
2. Create a backup of the CCNet installation directory (the project artifact directories can be excluded as they could be large considering the size and number of build logs)
3. Install the new version of CCNet over top of the existing installation (to the same installation directory). The installer will not be able to register the service or create the virtual directory; however, as the same directory will be used this does not matter.
4. Replace the new ccnet.config file with the backed up copy (ccnet.config.old). Restore any changes to the *.exe.config file, dashboard.config file, or xsl files from the backed up copy.
5. Try starting the ccnet console and resolve any required changes to the ccnet.config file. See the release notes for a list of configuration file changes in the latest version. If you use CCService, stop the console application and start CCService at this point.
6. Verify that the webdashboard is accessible and that all projects are started, have the correct version and their build log render correctly.
7. Download the CCTray installer from the Dashboard, install it locally and verify that it connects to the server/dashboard and that the projects display correctly.
8. Everything should be working now and the installation should be complete. If there were any problems encountered during the install, stop CCNet and then restore the previous version from the backup folder.

Pessimistic Approach:

1. Install the new version of CCNet to a different installation directory. The installer will not be able to register the new service or create the new virtual directory - these will be handled later.
2. Copy the ccnet.config and all .state files from the previous installation folder into the new installation directory. Merge any changes from the application configuration files (ccnet.exe.config, ccservice.exe.config, dashboard.config) into the new configuration files. Merge any changed stylesheets into the new stylesheet folders (in both the server and dashboard xsl folders). Also copy the project artifact directories from the previous installation folder.
3. Stop the previous version of the CCNet server (either by closing the console window or stopping CCService)
4. Start the new version of the CCNet console and resolve any problems with the ccnet.config file. See the release notes for a list of configuration file changes in the latest version.
5. Create a new virtual directory for the /dashboard folder (eg. include the installation version in the virtual directory name).
   Ensure that the directory has script, but not execute permission (to support downloading the CCTray installation). The <webURL> property in the ccnet.config file will need to change to reflect this new virtual directory name.
6. Verify that the webdashboard is accessible and that all projects are started, have the correct version and their build log render correctly.
7. Download the CCTray installer from the Dashboard, install it locally and verify that it connects to the server/dashboard and that the projects display correctly.
8. If you are using CCService, register the new service using the command:

   %SystemRoot%\Microsoft.NET\Framework\v1.1.4322\installutil.exe /ServiceName="CCService <version>" ccservice.exe

   From version 1.3 onwards, CCNet is based on Dot Net Framework 2.0, so change the above to :

   %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\installutil.exe /ServiceName="CCService <version>" ccservice.exe

   
   Replace '<version>' with the version of CCNet that you are installing. Start the service.

9. Everything should be working now and the installation should be complete. If there were any problems encountered during the install, stop the new CCNet server and start the old CCNet server.