Calling Custom Targets in Team Build, Part 3

I’ve done a couple of posts now on calling custom targets during a Team Build build – this one focused on calling custom targets in the solution/project being built, and this one focused on calling custom targets in your TfsBuild.proj file itself before/after the compilation of individual solutions or configurations.  In the past week I’ve…

3

The CompilationOutputs Item Group

I’ve mentioned the CompilationOutputs item group we added in TFS 2008 before in passing (see this post, for example), but never given it the attention it deserves…  This item group is built up over the course of the Compile / CompileConfiguration / CompileSolution targets, and by the end of the build it contains the full…

4

A Minimal TFSBuild.Proj File

A fair number of people seem to want to use Team Build to kick off their own pre-existing build scripts that have nothing in common with the process defined in Microsoft.TeamFoundation.Build.targets.  While we don’t typically encourage this, enough people want to do it that I figured I should finally post an example.  So – the…

3

Associating changesets and Work Items Since the Last Successful Build

We got a forum post the other day on whether changesets and work items could be associated since the last Successful build.  Some of you may be thinking "Isn’t that how it already works?"  Actually, it’s not quite how it works.  Changesets and Work Items are, by default, associated since the last "good" build, where…

3

Attaching Custom Data to a Build

In Orcas, we introduced a generic information storage for builds – internally this is used for all build steps, associated changesets/workitems, etc.  You can use it to attach arbitrary data to a build (and later retrieve it).  Here are a couple of quick code snippets to illustrate these two cases. To attach a single name/value…

2

Orcas RTM Object Model Documentation

The official Orcas RTM OM documentation was posted a while ago, and I neglected to blog about it!  It’s available here: http://www.microsoft.com/downloads/details.aspx?FamilyID=6466b53d-d80b-4c31-8f5c-dfb5d32e9411&DisplayLang=en.  Make sure to follow the instructions for viewing it after downloading: Method 1 Double-click the .chm file. In the Open File-Security Warning dialog box, clear the Always ask before opening this file check…

0

Tech*Ed 2008

If you are planning on attending Tech*Ed Developers in sunny Orlando this year, I’ll be manning the Visual Studio Team System 2008 Team Foundation Server (Version Control and Build) demo station (quite the name, eh?) for about 22 hours over the course of the four day event.  Please stop by and say hello, ask some…

1

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