CruiseControl.NET Converted to .NET 3.5
Over the week-end we finally upgraded CruiseControl.NET to use .NET 3.5. At the same time we branched the trunk and updated the version number for the trunk to 1.6.
This is good news in two ways:
- This means that the 1.5 release is finally marked as finished – there will be no new functionality added to it. There is still the potential for bug fixes, but hopefully these will tail off and we will be able to finally close off the 1.5 release (like we have the 1.4.4 release).
- CruiseControl.NET can finally start to use some of the goodies in .NET 3.5. This includes Linq, some multi-threading improvements, ASP.NET 2.0, etc.
At the moment CruiseControl.NET does not use anything from .NET 3.5, but we can look forward to this changing in the near future 
When we were debating whether to change to .NET 3.5 or not, we had one person ask why not wait a few weeks for the .NET 4 release and go straight to that? The answer is very simple – we are trying to ensure that CruiseControl.NET also runs on Mono. This means people on non-Windows OS’s can use it as well. Unfortunately, from what I have seen, there is no timeframe for implementing the new .NET 4 functionality into Mono yet, so we will have to wait and see what happens on that front.
But when Mono does have .NET functionality, I will be pushing to upgrade faster this time around…
Miguel de Icaza has a blog post here: http://tirania.org/blog/archive/2010/Feb-17.html where he says Mono 2.8 will ship with 4.0 support and will arrive a couple of months after .NET 4.0 ships. The relevant section is at the end of the post under “Policy Changes”.