I managed to get each project set up independently.  I hightly recommend starting with the latest CCNet bits.  I upgraded after I had 0.6 working and regretted it.  Open source folk tend to get a little inconsiderate with breaking expected features, config and interface.  Its free, its their perogative. 

One thing I found with version 0.8 is that you really should stick to absolute file paths for any config path you specify.  There is a new "WorkingDirectory" at the project level.  It seams inconsistently handled when using relative paths in other sections of the config file. 

Eventually, I got 0.8 working.  I have a cruise.build file whose purpose is to clean the project directories, get vss latest source, and call the actual build file that is retrieved from the source project.  In addition, it copies the result of each project build to any necessary consumer projects before they can be built. 

The default target "run" performs the whole solution build.  Each project has a target for: run-, clean-, get-, copyDependencies-, build-.  The build target calls the project specific nant build file in the source directory after the get- retrieves it.  The called build compiles to a directory "build" parallel to the source directory.  The cruise.build file expects this and copies artifacts from the "build" directory of the compiled project to the "source" directory of any project that uses that assembly.  This means a "solution build" must occur before any single project build will work.  That's fine.  I create a Solution project in ccnet.config.  I have a faked out sourcecontrol config block (vss path points to a deep image directory within one of the projects) and specified a forceBuild once per day.  That's my nightly build.  It also calls the target deploy-webProject.  This backs up web.config, deploys the project to two dev servers, then replaces web.config.  The first thing to do is force a build of the solution.  Then, once each project is set up initially, the source control monitor can take over.  I forced each individual project just to get each project into a successful state.

All my projects copy their log to the same web dashboard.  This works out great.  Thre project name is listed with each report. 

The ccnet tray is so sweet.  I love watching the build happening and then the "woohoo" when it all works.  I read a post on attaching lava lamps to X10 autmoation controls to indicate the build state via retro coolness. I'll link to that tomorrow