使用 TFS 标签，如 SourceSafe 标签 [英] Using TFS Labels like SourceSafe Labels

问题描述

我们有一个相当标准的发布程序，使用 Visual Source Safe 在发布之前标记构建.这使我们可以在出现任何问题时从该标签进行获取，并在需要更改时使用它进行分支.

We have a fairly standard release procedure using Visual Source Safe for labeling a build before it is released. This allows us to do a get from that label if there are any problems and use it to branch if changes are necessary.

我们有几个不同的项目，并且总是使用构建版本号进行标记.例如V1.0"

We have several different projects and always label using the builds version number. e.g. "V1.0"

在将一些项目移至 TFS 后，我们注意到如果您尝试使用与其他解决方案相同的版本号进行标记，例如解决方案 A 和解决方案 B 都发布了V1.5"，那么 TFS 不会让您这样做，因为标签名称是全局处理的.在阅读了一些关于该主题的博客后，这些博客讨论了 TFS 标签如何不是一个时间点而是一组文件，我想我们将不得不开始在标签中包含项目名称以解决这个问题，例如标签为Project A V1.5"和Project B V1.5".这听起来像是正确的方法吗?

After moving some projects to TFS we have noticed that if you try to label using the same version number as another solution e.g. Solution A and Solution B both release "V1.5" then TFS will not let you do this as the Label name is treated globally. After reading a few blogs on the subject which discusses how TFS labels are not a point in time but a collection of files I am thinking that we will have to start including the project name in the label to get around this e.g. label as "Project A V1.5" and "Project B V1.5". Does this sound like the right approach?

推荐答案

如果您还没有阅读 Brian Harry 的 为什么 TFS 标签不像 SourceSafe 标签，请这样做.

If you haven't read Brian Harry's Why TFS labels aren't like SourceSafe labels, please do.

基本上你的问题的答案是肯定的！

Basically the answer to your question is YES!

这篇关于使用 TFS 标签，如 SourceSafe 标签的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！