1. Download the installation package from Sourceforge.net. As of writing this article, the latest version is available here.
2. Run the installer. This will copy the files you need and create the IIS site/virtual directories needed to access Cruise Control .NET from your browser.
3. Open your Internet Information Services (IIS) Manager (Start -> Run -> inetmgr )
4. Create a new website point the site to <INSTALL PATH>\webdashboard.
5. Change the bindings for the new site to a unique port. ( I use port 90 and the CCNET is then accessed via http://localhost:90)
6. Open the application pool created for this site and change the 'Managed pipeline mode' to 'Integrated'.
7. Open the services manager (Start -> Run -> services.msc) and start the Cruise Control .NET service.

My Cruise Control .NET implementation consists of numerous development projects each with multiple different CCNET projects associated with it (one per environment per branch). In order to make the projects more maintainable, I have created a separate configuration file for each development project.

Defining variables and separating ccnet.config configuration file into smaller files allows for easier maintenance as the number of projects as time went on.

Defining and using variables

Variables can be defined using the following format

<cb:define KEY="VALUE" />

To reference that variable later in the configuration file, simply use $(KEY)

Check out the Cruise Control .NET website for complete explanation of variables using the pre-processor.

Separating the configuration files

<!DOCTYPE cruisecontrol [
<!ENTITY PROJECT_NAME SYSTEM "file:project.xml">
]>
<cruisecontrol xmlns:cb="urn:ccnet.config.builder">
&PROJECT_NAME;
</cruisecontrol>

project.xml would, then, contain the regular xml configuration for a Cruise Control .NET project:

<?xml version="1.0" encoding="utf-8"?>
 <project name="My Project" category="A Category">
  <workingDirectory>MyProject</workingDirectory>
  <artifactDirectory>MyProject</artifactDirectory>
  <webURL></webURL>
  <triggers>
   <intervalTrigger seconds="900" buildCondition="IfModificationExists" />
   <scheduleTrigger time="04:00" buildCondition="ForceBuild" />
  </triggers>
 <labeller type="svnRevisionLabeller">
   <pattern>Version {major}.{minor}.{build}.{revision}</pattern>
   <major>1</major>
   <minor>0</minor>
   <url>$(SvnBaseUrl)</url>
  </labeller>
<sourcecontrol type="svn">
   <trunkUrl>$(SvnBaseUrl)</trunkUrl>
   <workingDirectory>$(BaseDirectory)</workingDirectory>
   <cb:SvnOptions />
  </sourcecontrol>
<tasks>
   <nant>
    <executable>$(NAntExecutablePath)</executable>
    <baseDirectory>$(BaseDirectory)</baseDirectory>
    <targetList>
     <target>dist.deploy</target>
    </targetList>
   </nant>
  </tasks>
 <publishers>
   <xmllogger />
   <cb:include href="EmailConfig.xml"/>
  </publishers>
</project>

On caveat with this idea is that changes to the separate configuration files are not recognized until the cruise control is restarted by either restarting the service or modifying the ccnet.config file.

Building and Deploying ASP.NET Web Applications

The NAnt target below is a full parameterized call to MsBuild.exe to compile any solution. ThoughtWorks.CruiseControl.MsBuild.dll provides an MSBuild logger that allows Cruise Control .NET to report the bulid output.

Parameters

MSBuildPath - The path to the MsBuild executable.

For .NET Framework versions 2.0 and 3.5  on a 32-bit Windows OS, use C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MsBuild.exe
For .NET Framework version 4.0, use C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MsBuild.exe

SolutionFile - The relative path from the build file to the solution file. Fully qualified paths are also allowed.

SolutionConfiguration - "Release" or "Debug".