在 TFS 2010 中的集合之间移动项目
我想在集合之间移动一些项目，但我找到的唯一资源就是这两个资源，并且它们没有解决如何在 TFS 2010 中执行此操作：
有人知道任何其他资源或了解如何将项目从一个集合移动到另一个集合吗？
I'd like to move some projects between collections but the only resources I've found are these two and they don't address how to do this in TFS 2010:
Does anyone know of any other resource or has information on how to move a project from one collection to another?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
长期以来，Man 一直想知道在这些包罗万象的集合中组织项目的最佳、最有效的方式是什么。随着项目的增长，集合中存储的内容如此之多，以至于将所有项目保存在一个集合中几乎是不可能的。
最初，我们从 DefaultCollection 开始，然后放弃单一的想法，开始为每个客户创建一个 Collection...然后我们从这个出发，开始创建容纳各种项目的广泛类别，但是我们的许多客户有太多的交叉 -在类别之间……然后我们确定了一个模型……但那时我们已经在特定项目上进行了大量开发，因此将一些项目转移到我们的最终存储模型中将不得不等待。好吧，我们今天进行了迁移...将项目从一个集合中的一个团队项目转移到另一个集合中的另一个团队项目中。
这是成功的。我们仍然没有完全使用所有工作项，并且我们的总体源代码控制相当线性。我们认为失去项目的历史对我们来说是可以接受的。我们并没有完全删除一些东西，所以如果我们需要返回，我们可以......但知道我们现在永远不需要这样做。
因此，为了不再让您费力地阅读我的独白，以下是我们采取的步骤：
看起来步骤很多，但它的工作原理非常明显。您只需制作现有项目的外部副本，删除源代码管理绑定的所有实例，然后将其添加回源代码管理中您想要的位置。理想情况下（就像 Subversion 一样），您可以只导出一个项目，然后您就可以在那里选择未绑定的版本...只是使用 TFS 时，代码中分散了更多绑定...并且其中大部分都可以轻松删除在项目和解决方案清单中。
不管怎样，你可能会在比你阅读本文所用的时间更短的时间内完成它......希望它有所帮助。
Throughout time, Man has wondered what would be the best, most efficient way to organize Projects within these all-encompassing Collections. There is so much stored within a collection as projects grow, that it seems almost impossible to keep all Projects in a single Collection.
Initially, we started with a DefaultCollection, then moved away from the singular idea and started creating a Collection per client...then we moved from this and started creating broad categories that housed various projects, however many of our clients had too much cross-over between the categories...and then we settled on a model...but by then had done so much development on particular projects that moving some into our final storage model was just going to have to wait. Well, we did the move today...brought projects from one Team Project in one collection into another Team Project in another Collection.
It was a success. We are still not fully using all Work Items and our general Source Control is fairly linear. We decided that losing the history of the Project was ok with us. We didn't totally delete things, so if we ever needed to go back, we could...but knew we'd never really need to do that at this point.
So, to stop making you wade through my monologue any longer, here's the steps we took:
It seems like a lot of steps, but it's really obvious how it works...you're just making an external copy of the existing project, removing all instances of the source control bindings, then adding it back into source control where you want it. Ideally (like with Subversion), you could just export a project and you'd have the unbound version there for the picking...it's just that with TFS there's more bindings scattered throughout the code...and most of it is easily removed in the project and solution manifests.
Anyways, you'll probably have it done in a shorter time than it took for you to read this...hope it helps.
您可以查看 TFS 集成平台（以前称为 TFS 到 TFS 迁移工具）。它具有用于将源代码从一个 TFS 实例移动到另一个实例的实用程序，如果您也想从一个集合移动到另一个集合，那么它应该可以工作。
You could look at the TFS Integration Platform (formerly called the TFS to TFS Migration Tool). That has utilities for moving source code from one instance of TFS to another, which should work if you want to move from one collection to another as well.
TFS 集成工具可以迁移到新集合，但所有日期都会变成迁移日期，并且所有内容的 ID 值都是新的。我的自定义模板也确实存在问题。这在我的环境中行不通，因此我正在对同一源数据库进行多次升级，这样我就不会丢失此信息并销毁重复项。
The TFS Integration tool can migrate to new collections, but all the dates become date of migration and the ID values for everything is new. I did have issues with our customized templates too. This wouldn't fly in my environment, so I am doing multiple upgrades of same source databases so I don't lose this information and destroy the duplicates.