MSBuild tasks for Team Foundation Server

I’ve experienced editing Team Foundation Server builds by hand and I didn’t like it. Maybe I’m missing something here, but it’s very complex and troublesome. I want some more ‘advanced’ stuff in my build process, like preparing a build for our test environment but also for our production environment. I want to have different configuration files for both, with different connectionstrings for example. And I want my ClickOnce application to be deployed on the correct location with the right version numbers. And I want continues integration with CruiseControl.NET.

That’s not overly complex when I just use CC.NET and MSBuild. But with TFS I cannot extract the build onto my local desktop and change stuff until I think it’s right. I’m interfering with the normal continues builds and other teams don’t like this.

So I decided to leave TFS Build for what it is and use CC.NET and MSBuild stand-alone. Problem is, I still need to checkout files to increase version numbers and such. But I cannot find any MSBuild tasks related to Team Foundation Server!

So my question is…

  1. Are there any MSBuild tasks that can talk to Team Foundation Server?
  2. Is anyone interested in these if I’d develop them?
  3. Is it a good idea to host this stuff on Codeplex?

I’d really like to know answers to these. Email to me directly or respond here. Thanks.

You may also like...

5 Responses

  1. I’ve got those, but they only have 1 task to check on changes in a workspace. I need tasks to checkout, checkin, etc.

  2. Richard P says:

    First of all, you can control your build by editing the TFSBuild.proj file in the source repository (at least in TFS Orcas, back me up on 2005)

    Second off, all the custom tasks can be found in C:Program FilesMSBuildMicrosoftVisualStudioTeamBuildMicrosoft.TeamFoundation.Build.targets

  3. Yeah, I know…

    But do you use Continues Integration outside of Visual Studio/TFS? Because I’m on TFS v1 and CC isn’t included. So I’m using CruiseControl.NET but it’s very hard to run and test this. As far as I know, it must be done on the server itself and cannot be tested locally… Kind of a bummer, as you screwing up the build when you’re adding new stuff. And besides that you might also mess with other build process along the way.

    That’s why I chose to stay of TeamBuild and stay with MSBuild for now and ignore the TFS build possibilities until I find a better way.

  4. Mr B says:

    Have a look at this URL:

    It is a MSBuild task for retrieving the drop folder for a build specified.

Leave a Reply

Your email address will not be published. Required fields are marked *