TFS: Labels vs Changesets

tfs label changeset
laconicdev picture laconicdev · Jun 5, 2009 · Viewed 45k times · Source

I am trying to come up with best practices regarding use of TFS source control. Right now, anytime we do a build, we label the files that are checked into the TFS with the version number. Is this approach better or worse than simply checking the files in and having the version number in the comments? Can you then use the changeset to go back if necessary or the labels are still more versatile?

Thanks!

Answer

Alex picture Alex · Jun 5, 2009

They have two different purposes, ChangeSets are when the files have actually changed and you wish to keep a permanent record of that change. Labels mark a certain version of the files so that you can easily go back to that point. Unless your build actually changes files under source control and you wish to record these changes. You should be labeling.

Also, labeling is much less resource intensive. And you can have multiple labels on the same version of a file.

Related questions

How do I figure out which changeset a label in TFS was applied to?

We're using Team Foundation Server and we are using Labels to create points in our version history where specific versions (either internal or external) were produced. Right now we were wondering if a particular changeset was done before or after …

Read More
TFS 2010: history lost after moving a folder

In order to clean up my project structure, I moved a folder into another (new) folder through the TFS Power Tools Shell-Extension (Rename/Move). After checking the history at the new place, the move is the only entry. (I tried …

Read More
How to retrieve the hash for the current commit in Git?

I would like to retain (for now) the ability to link Git changesets to workitems stored in TFS. I already wrote a tool (using a hook from Git) in which I can inject workitemidentifiers into the message of a Git …

Read More