Visual Studio 2010 and CruiseControl.NET
Recently we upgraded from Visual Studio 2008 to 2010, which impacted our continuous integration and automated build process. For continuous integration we're using CruiseControl.NET. At the beginning of our Visual Studio 2010 upgrade we decided not to install Visual Studio 2010 on our continuous integration server. Because CCNET is basically just running an MSBuild script, I figured all I needed was .NET 4.0 framework installed which would be a quicker, easier, cleaner (and more best practice-y) than installing the full Visual Studio 2010. Well it didn't quite turn out to be that way and I eventually just ended up installing Visual Studio 2010 on the box. Here are my reasons: After converting my solution and project files, and then modifying the CCNET config to use the .NET 4.0 version of MSBuild instead of .NET 3.5, the first build attempt barfed with a bunch of errors like this: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1835,9)