Orcas SP1 TFS Build Changes, Part 2

As promised, here are some more details on other SP1 changes for TFS Build.  3. Detect test results. In Whidbey, a failed test would result in a failed build – builds were either Succeeded or Failed, so there wasn’t really much middle ground.  In Orcas we added two new build status properties, CompilationStatus and TestStatus;…

3

Orcas SP1 TFS Build Changes

Brian Harry put up a post on the improvements that will be available in the upcoming Team Foundation Server 2008 SP1 release.  Here’s some more in depth info on two of the TFS Build changes: 1. Conditionalize builds on the trigger. There are actually a few changes here…  Essentially we exposed a property on IBuildDetail…

10

Solution-Specific Output Directories in Visual Studio 2008 (Orcas)

In an earlier post I described how one can, in Orcas, preserve the output directory structure used in a standard IDE or desktop build.  It seems that many people are looking for a simple approach, however, to augmenting the standard Team Build output directory by putting the outputs of individual solutions into individual subfolders (I…

5

Overriding the ToolsVersion for Your Projects in Team Build

Recently I got a question about how to compile projects against multiple .NET Frameworks (e.g. 2.0 and 3.5) in Team Build.  MSBuild added support for this sort of thing in the 3.5 framework (they call it multi-targeting), but it is not particularly easy to take advantage of it in Team Build.  Here’s the text of…

1

Modifying the ConfigurationFolderPath RecursionType in Team Build 2008

In TFS 2008, TfsBuild.proj files can be located anywhere in source control, not just in $/TeamProject/TeamBuildTypes, as was required in TFS 2005.  As a result, we changed the default recursion type used to download files from the configuration folder path (the location of TfsBuild.proj) to RecursionType.OneLevel, meaning that only the contents of the exact directory…

9

Team Build 2008 Property Reference

There are lots and lots of MSBuild properties available to Team Build 2008 build definitions, most of which are probably unknown to the majority of users.  As such, I’ve tried to compile a comprehensive list of these properties so that they can (hopefully) be more widely used.  I’ll do the same thing at some point…

17

Calling Custom Targets Within Team Build, Part 2

First of all, sorry for the long delay between posts…  Things have been a bit crazy around here trying to meet various deadlines lately, and blogging fell right off my radar for a while.  Having said that, I’ve got a pretty big backlog of posts to get done, so hopefully I’ll get a bunch posted…

4

How Would You Spend $100 On MSBuild?

The MSBuild team is looking for some feedback from the community to keep their “vision” for the next version of MSBuld aligned with their customers wants and needs.  They’ve got a blog post up here that asks for you, the MSBuild experts out there, to rank various potential new features they could work on.  Here…

2

How to: Fail a Build When Tests Fail

Got an email from Martin Woodward this morning asking: What would be your preferred way to fully fail the build on test failure rather than partially succeed the build? A bit of background – Team Build 2008 marks builds as Succeeded if no errors are encountered during the build process, Partially Succeeded if compilation succeeds…

7

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