As Robert Horvick and Rob Caron have both mentioned, Mario Rodriguez has started a blog on version control: http://blogs.msdn.com/mrod/. In his first post, The Start, he talks about his background and the topics he intends to cover. If you have features that you really want to see in future releases of Team Foundation Server version control,
I stumbled across the following pages on MSDN that provide step-by-step introduction to the basics of extending Team Foundation Server.
Walkthru:Extending Process Templates
Walkthru:Extending Project Creation
Walkthru:Extending Work Items
Walkthru:Extending Test Types
Walkthru:Build System Customization
Walkthru:The Version Control Object Model
Extending the Reporting Engine
I recently had to put together a list of links to code samples. This isn’t even close to comprehensive, but it should help you get going if you are looking for something.
How to Write a Team Foundation Version Control Add-in for Visual Studio
Team Foundation Version Control client API example (RTM version)
Displaying the sizes and dates of files in the server
Displaying the labels on a file,
On internal mailing list, someone asked how to do this, and I thought it’s worth sharing. You can get a Changeset object using its artifact URI (aka link) via VersionControlServer.ArtifactProvider. Here’s how that would look like, based on modifying code from James Manning’s blog posthttp://blogs.msdn.com/jmanning/archive/2005/09/21/472524.aspx.
First there was Jeff’s RSS feed generator for version control. Then Abhinaba used it as a starting point for his RSS feed generator for team build. Naren has now posted an RSS feed generator for work item tracking. A quick web search yielded an RSS feed generator for SharePoint.
In addition to the MSBuild documentation on MSDN and the MSBuild team blog, there is an MSBuild wiki on Channel9. I had seen it before, but forgotten about it until I saw it mentioned in one of Chris Sells’ old blog posts (My First MsBuild Task).
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,
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”
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:
Open the Visual Studio Team System Integration folder from the VS 2005 SDK.
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,