Building VC++ 2005 Projects With Team Build 2008

MSBuild introduced a multi-targeting feature in VS 2008 that allows it to build managed code projects that target previous versions of the .NET Framework (and all associated tools – the Microsoft.Common.targets file, the MSBuild engine itself, etc.).  Unfortunately, there is no corresponding functionality for VC++ projects, since these are still not MSBuild compatible project files. …

5

Error MSB3021 and Team Build

The error message “error MSB3021: Unable to copy file “<filename>” to “<output location>”. Access to the path ‘<output location>’ is denied” occurs when the MSBuild Copy task cannot overwrite an existing read-only file.  Typically in Team Build this error will occur because (a) there seems to be an issue in MSBuild where the same file…

6

Running Unit Tests for Individual Configurations with Team Build

The default behavior of Team Build when running unit tests is to run them for each configuration defined for the build.  That is, when you specify configurations for compilation (e.g. Debug|Any CPU and Release|Any CPU) you are also specifying them for tests.  This is true of both VS TFS Build 2005 and VS TFS Build…

2

Using the SetBuildProperties Task to Update the Log Location for a Build

One of the new tasks available in Team Build Orcas (VS 2008) is the SetBuildProperties task.  This task allows you to modify any of the settable properties of a BuildDetail object directly from you MSBuild script (TfsBuild.proj).  The settable properties include: BuildNumber.  This is often displayed in the GUI as Build Name. CompilationStatus.  A string…

2

Fancy New Command-Line Options For MSBuild

A while back I had a post on the modified command-line options for file logging in MSBuild in the 3.5 .NET Framework.  The MSBuild team has since added some cool new command-line options here that will be available in the RTM version of VS 2008 (which will include the 3.5 .NET Framework).  In particular, you can…

3