Changesets and updating work

Rated 3.82/5 based on 877 customer reviews

I’ve picked up some interesting tips and tricks over the last couple of months.

Most of these customizations were already available somewhere on the web (see for example Ewald Hofman’s excellent series on customizing Team Build 2010, which in general applies quite nicely to TFS 2012 as well), but some modifications are my original work in that I did not find it anywhere else on the web.

Recently I got involved in implementing Team Foundation Server 2012 for a large development project.

And even though I’ve worked with several versions of TFS over the years, this was the first time I really dove into the options for customization beyond your average workflow modifications.

We have three streams (dev, qa, prod), Using Teams, we require unique approval when delivering to qa (review) or to prod (approval), but not for delivery to dev.

Currently, if you’re using Team Build, you can check code in and build – and the build report will associate the checkins (and their associated work items) with the build. however, if you want to see the changesets that were merged in the build report too, you’re stuck.For more information about comparing databases with SQL Compare, see Worked example - comparing and deploying two databases in the SQL Compare documentation.You can update to a specific version using your source control system and SQL Compare.Assuming the default build template, this is done as part of the “Compile, Test, and Associate Changesets and Work Items” parallel sequence.Look for a sequence like this in the template editor: Now if your team is anything like my team, they will not deliver a specific piece of functionality or fix a particular bug in a single checkin. Client; namespace Custom Activities You see that this is a two-way association.

Leave a Reply