= Quick Guide for Setting up Cruise Control .NET =

== Installing ==
 * Install Windows Server 2003 R2 (or newer) and all available service packs and hotfixes
 * Install .NET Framework 3.5 SP1 (if not already installed by the previous step)
 * Copy the c:\Program Files\MSBuild folder from a machine that has VS 2008 installed to the C:\Program Files\MSBuild folder on the server.
  * See http://www.cynotwhynot.com/blog/post/MSBuild-missing-MicrosoftWebApplicationtargets.aspx for more information
 * Download the latest CruiseControl.NET installer from: http://ccnet.thoughtworks.com/CCNet-builds/
  * This tutorial uses CruiseControl.NET-1.5.6745.1-Setup.exe
 * Run the CruiseControl.NET installer. I installed with the default settings.
 * If you're connection to a Subversion Repository like CodeResort, install the Subversion Command line client too. Download the latest Apache build from: http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=8100.
  * This tutorial uses Setup-Subversion-1.6.6.msi)
 * You now have a Continous Build server installed, but you need some configuration to make it work.
 * Open the c:\Program Files\CruiseControl.NET\server\ccnet.config file in notepad
 * Use the available documentation from http://ccnet.thoughtworks.com/ or look at the example ccnet.config file.

== Running CruiseControl.NET ==
 * To test your config, start CruiseControl.NET using the shortcut on the desktop.
 * If you change the config file, it is automatically reloaded by CruiseControl.NET
 * You will need a trigger section to run builds automatically. You can also force a build using the Dashboard on http://localhost/ccnet 

== Troubleshooting ==
 * If you're having trouble compiling projects or solutions on the build server, try to install the latest Windows SDK (which has .NET Framework support), or install Visual Studio Express Edition. You do not need to do a full Visual Studio 2008 installation.
 * When running the CruiseControl.NET Windows Service, you might get problems accessing subversion repositories or other resources. Try running the service using a local windows account that you have used to log on to the server, and that has access to networked resources that your build server needs.
 