I've often had issues getting an automated build process to run correctly with Cruise Control and MSBuild. It seems that when ever there is more than one project file introduced into the solution you start getting issues with your automated build server. What usually ends up happening is you end up installing Visual Studio on the Build server to figure out why its not building and in most cases its MSBuild getting those binding wrongs between the various projects when it gets the latest version of your solution out of version control. What I found actually helped was to actually check out the solution file on the build server create the proper bindings and then check the file back in, its seemed once I had done this it would remember the bindings and not re do them every time I did a build. It seemed odd but the actual binding information appears to be stored locally outside of the solution and proj files that are checked into source control which I found rather odd.. oh well its works..