One way of setting up CC.NET and VSS is that CC.NET is responsible for getting the latest version (setting the attribute autoGetSource to true of the sourcecontrol node in the ccnet.config file) or NAnt by using the vssget task of NAntContrib for compiling the sources by NAnt. I always use the csc task instead of the solution task, therefore it is necessary to have a clean version of VSS, because VSS does not automatically delete files locally that have been deleted in the VSS database.

An alternative and better way is to set a shadow folder in VSS. A shadow folder contains a copy of the most recently checked-in version of each file in the project. This is exactly what we need for compiling the sources.

That way is CC.NET only using VSS for monitoring changes in the VSS database and/or labeling.

Thoughtworks released a new version of CruiseControl.NET.
More information about the changes can be found here.

Thoughtworks released a new version of CruiseControl.NET.
More information about the changes can be found here

More information about CruiseControl.NET and the new features can be found here.

CruiseControl.NET is a continuous integration tool we have set up for our current project. It automatically builds when there is a change in source control (VSS, CVS, ClearCase, etc), and it reports it in a nice web layout with all the build, nunit, fxcop results.

There is also a nice tray application that can be installed on the developers pc's which indicates the status of the builds, for example it becomes:

• green: build is successfull
• yellow: server is currently building
• red: build is failed
• gray: server is unavailable

It's always a moment of truth when checking in code and hoping that the tray application remains green

We use NAnt as build tool and NUnit for unit testing. The only thing to pay attention for is that for example deleted files in VSS remains in the working directory and therefore still be included by NAnt. Therefore we setup a small integration server where VSS, Microsoft.NET SDK 1.1 and CruiseControl.NET is installed. The build script that is called by CruiseControl.NET does basically the following tasks:

• delete all source files
• get latest version of sources
• get latest version of buildscripts
• build the sources
• test the binaries

(buildscripts, NAnt and NUnit are stored in VSS)

NAnt can do operations on VSS if you download NAntContrib, there you have a set of additional tasks like 'vssget', 'vsslabel', etc. Note that it is a real advantage of storing your buildscripts in VSS so that CruiseControl.NET always uses the latest buildscripts.