This post originated from an RSS feed registered with .NET Buzz by Sam Gentile. Original Post: CCNet 1.0 RC1 Released!!! Feed Title: Sam Gentile's Blog Feed URL: http://samgentile.com/blog/Rss.aspx Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More! Latest .NET Buzz Posts Latest .NET Buzz Posts by Sam Gentile Latest Posts From Sam Gentile's Blog

I was really thrilled to hear via Mike that this was out, just in time for my INETA CapeCod.NET talk. I don't know what I (and many others) would do without our daily dose of Mike in the morning who always informs me of critical things like this that I wouldn't have known about right away as mailing lists and newsgroups just don't work/scale for me personally. When I talk about the Power of Blogging, and why that model works for me, a large reason is Mike. This list of Major changes is drool worthy IMHO, and the ones I have marked in Bold are very important to me:

Major Changes

There are some big 'top level' changes in this release:

• CCTray has been completely re-written. The version that ships with 1.0 has configuration files that are incompatible with those used by prior releases. In other words, throw away all your old CCTrays, and use the new one. CCTray now ships with its own installer which you can distribute to anyone who wants to monitor your build server.
• The new CCTray has many more features than the old, and is much better for organisations or teams with multiple projects or build servers.
• CruiseControl.NET now has native MSBuild support for .NET 2 . Even if you call MSBuild from a NAnt script rather than CruiseControl.NET directly you'll want to look into using the CruiseControl.NET MSBuild XMLLogger and the MSBuild XSL files.
• The old (single project) web application has been deleted, and CCNet now only ships with the Web Dashboard.
• The main CCNet installer now ships with just the Build Server and Web Dashboard - use the separate CCTray installer for CCTray.
• Integration Properties (passed to NAnt, for example) have been changed to be CamelCased rather than period.separated so you may need to update your build scripts. These properties are now also passed through the <exec> and <msbuild> tasks.