Home/ Questions/Q 7739933
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T08:38:50+00:00

I’m trying to write a very lightweight build script which will basically just get

  • 0

I’m trying to write a very lightweight “build” script which will basically just get a few files from TF (based on a Changeset number). Then I’ll run those files in SQLCMD.

I’m using this:

tf.exe get c:\tfs\  /version:c2681  /force /recursive

However, this appears to get EVERYTHING, not just the files in changeset #2681. I’d like to be able to point it to the root of my tfs workspace, give it a changeset number, and have it just update those few specific files. Also, it appears to be getting older versions (perhaps what was current when changeset #2681 was checked in)?

Is there a way to get just those specific files, WITHOUT needing to call them out specifically in the tf get itemspec?

EDIT: I actually had to add the /force option in order for it to do anything at all. Without force, it doesn’t appear to even retrieve from the server a file I deleted locally, that’s definitely in the changeset.

thanks,
Sylvia

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The TFS server keeps track of what each workspace contains1. Any changes made locally with non-TFS client commands (whether tf.exe, Team Explorer or another client) will lead to differences between the TFS Server’s view and what actually exist.

    The force options on the various clients just gets everything removing such inconsistencies (effectively resetting both what is on the client and what the server thinks is there).

    When you perform a get against a specified version (whether date, changeset or label) you get everything up to and including that point in time, whether on not specifically changed at that point. So getting

    tf get /version:D2012-03-30

    will get changes made on or before that date.

    To get only the items included in a changeset you’ll have to do some work yourself, using a command to get a listing of the content of a changeset and parse that to perform the right actions (a changeset can include more than just updates and adds of files2).

    It seems to me that if you want to perform a build at each changeset affecting a particular TFS folder you would be better off looking at using TFS Build which is all about doing exactly that – avoid reinventing the wheel – and focus on the build part (other continuous build solutions are available).

    1 This will change with TFS11 local workspaces.

    2 Eg. handing the rename of a folder will take some non-trivial work.

    • 0