Buck Hodges
Azure DevOps (formerly VSTS and Team Foundation Server)
Latest posts
Don’t override CoreCompile
There have been several times when folks have needed to run a custom target prior to building each solution (or project) in Team Build. Unfortunately, there's no good way to do this. Manish Agarwal describes (mostly) how to do it in his post, How to call a custom target after building each individual solution (sln) in Team Build? The solution he gives involves overriding the CoreCompile target.The CoreCompile target, along with many other Core* targets, is changing for the next release of Team Foundation Server. The changes are due to the need to support new features in the product, a...
Putting the build number in your binaries
Jeff Atwood has a nice post on how to get Team Build to put the build number in the assemblies it builds. Adding the Build Number to your Team Build binaries If you're using Team Build, you may want to "tag" the binaries produced with the name of the build. In order to do this, we'll customize the Team Build script (TFSBuild.proj) for the project, hooking in to the default Team Build BeforeCompile event.
Intellisense while editing Work Item Types
Back in April, Mariano Szklanny posted a tip on how to get intellisense in VS when editing the XML for a work item type. If you’re editing work item types, you will find useful having Intellisense in Visual Studio 2005:
More continuous integration with Team Build
Earlier, I mentioned Jeff Atwood's continuous integration approach. Here are a couple more approaches.Sondre Bjellås has decided to write his own continuous integration system for Team Build back in May (Making a Team System Automation Framework). It is called Automaton, and it's available on CodePlex. Automaton is a Continuous Integration engine for Microsoft Team Foundation Server. Automaton will monitor your source code repository and automatically run the correct team builds that you create within Visual Studio. Build reports can be view through a web site, and your development team can get ...
ClickOnce manifests and Team Build
Eric Charran has written a nice post on dealing with ClickOnce manifests in Team Build. Building a ClickOnce Manifest File with Team Foundation Services Team Build Issue: When building a ClickOnce application using Team Foundation Build Services, the goal is to modify the details contained within the .application deployment manifest file to conform to desired settings segregated by build type. This would allow Build Masters and Release Managers to build the application using different build types within Team Foundation Server and have the drops for those builds take on different deployment profiles. F...
Continuous Integration with Team Build
Jeff Atwood started out with the continuous integration with MSDN CI sample for Team Build. Then he made improvements to it and posted it as a A Kinder, Gentler Continuous Integration service for Team Foundation Server. You can use Abhinaba's build notification tools to keep track of how it's going. A Kinder, Gentler Continuous Integration service for Team Foundation Server In an earlier post, I documented how to set up Microsoft's unofficial Continuous Integration solution for Team System. I was a little.. perplexed.. by the code inside that web service. I took some time to refactor it and polis...
Two more ways to get build notifications
Abhinaba Basu posted his second Team Build power toy build notification app. Previously he had posted a Team Build RSS feed power toy. Today he posted his desktop notification app, which he calls BuildTicker. Team Build Ticker: parting gift I had blogged earlier about the BuildTicker tool which sits on the system tray and notifies of builds happening on the server. I have received many requests to get this tool. So here it goes. Get the executable from here and the sources from here. Since I am no longer working on the TFS team you can consider this as my parting gift :)
Team Build Extensibility
There's a document in the Visual Studio 2005 SDK that describes the extensibility points in Team Build. I have the April release of the SDK, so it's located at C:\Program Files\Visual Studio 2005 SDK\2006.04\VisualStudioTeamSystemIntegration\Team Build\Team Build Extensibility.doc. The SDK is a huge download, so I'm attaching the document to this blog post. Here's what's covered in the document. Understanding Team Foundation Build configuration files Order in which targets are executed by Team Foundation Build Extending Team Foundation Build Creating a Build Type Creating Custom Tasks Checking Out th...
Google Web Accelerator doesn’t mix with TFS
In the forum post Getting Latest Version Error (TF30063), a user was getting the error message "TF30063: You are not authorized to access Microsoft-IIS/6.0" when getting files from version control. I asked a bunch of questions, which the user answered, but that didn't really help. The user end up figuring it out. It turns out that the client computer had the Google Web Accelerator installed, and the web page caching was causing problems.I had seen anti-virus applications and firewalls causing problems (for example, random files being left writable after a get), but this was a new one. ...