CruiseControl.NET is distributed in 3 formats:

• Two Installers, one for CruiseControl.NET proper (the Server and Web Dashboard), and a second for the optional CCTray utility. The Installers are conventional Windows installation programs, which perform some useful early setup work for you, such as copying files to good locations, setting up a Virtual Directory for the Dashboard, etc. For most people starting out, this is the way to go.
• A binary zip file includes the same files as the installers but gives you more control over what you can do with them.
• A source zip which allows you to read or make your own changes to the CruiseControl.NET source code.

The binary zip file will give you several sub-folders:

• /server: holds the assemblies for the CruiseControl.NET Server, including both the The Server Console Application and The Server Service Application .
• /webdashboard: contains the ASP.NET Web Dashboard application
• /cctray: contains the assemblies for the CCTray application
• /doc: contains HTML documentation for CruiseControl.NET

With the binary zip file, you will have to manually configure IIS if you want to use the Web Dashboard, and you will have to manually install the service if you wish to run the Server that way. This is in addition to the usual, such as adding shortcuts to the Start Menu if you wish.

Select one of the links above for more detailed information on configuring the CruiseControl.NET applications. You will find links to the various kits on the Download page.

Unattended Installation

CCNet uses NSIS, the open source NullSoft installation package, to build the installer packages. To do a silent installation of CCNet you can use the /S command-line switch. For example, to install CCNet in silent mode, run the following command:

CruiseControl.NET-1.x-Setup.exe /S

The silent installation will install using the default installer options, which in general will overwrite the previously installed version of CCNet. You can also use the /D=output_folder option to specify a different installation location.

Windows message boxes may pop up during an install process, so this currently can't be automated reliably.