We are currently working on implementing a stronger Continuous Integration strategy at our office. Currently we have a single web application that is built a matter of seconds after something in our Subversion repository has changed. It then automatically deploys the newly compiled and hopefully "built" release to a file server for immediate testing by our BA/SA guys.

So in the process of trying to add more projects and improving what CCNet can do for us I ran across a cool little article (http://www.codeproject.com/KB/cs/Continuous_Integration.aspx) by Sean Chambers. In it he lists a lot of the popular tools that can be integrated with CCNet. One that I missed on the first read through is CCNetConfig. If you are familiar with editing CCNet config files to add projects and project settings, you know it can be a little tedious, especially when trying to remember the correct XML keys/values. CCNetConfig is a GUI that uses similar features of Visual Studio to help you setup Projects, Tasks, Publishers, and most anything you could possibly want.

Here is a screenshot of CCNetConfig in action:

It is worth mentioning that CCNetConfig can edit the CCNet Configuration file on a remote build server or machine, and thanks to ASP.NET the application pool will automatically recycle when you save and the changes are instantly put into place (NOTE: From good sysadmin standards you might not want to do this, or at least backup the original config file first).

All around this is a great tool and can save lots of time when you need to quickly turn up a new project in CCNet. CCNetConfig is available from CodePlex free of charge:

http://www.codeplex.com/ccnetconfig