从SVN迁移到TFS（如何处理外部）
所以我们正在尝试正确的 TFS，在大多数情况下你几乎可以弄清楚它，我们创建了一个测试项目并添加了它等等。一切都很顺利。我还没有真正理解的是如何处理外部项目，我们有两个大型项目，它们都引用一个共享核心项目，然后这两个解决方案的其他一些部分本身就是单独的项目，它们当然是外部项目出色地。
我们不关心历史（我们正处于可以彻底决裂的时刻），所以我计划走 1) 创建新的 TFS 2) 添加从 SVN 导出的项目的路线。
我的问题再次是如何处理外部因素 - 如果有人能给我指出正确的方向，那就太好了。
谢谢。
So we are trying out TFS right, for the most part you can pretty much figure it out, we created a test project and added it etc. All went well. The thing I haven't really grokked is what to do about externals, we have two large projects and they both reference a shared core project, and then some of the other parts of those two solutions are separate projects themselves which of course are externals as well.
We don't care about the history (we are at a point where we can make a clean break) so I was planning to go the route of 1) create new TFS 2) add projects exported from SVN.
Again my question is how to handle the externals - If someone coule point me in the right direction that would be great.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
与 Subversion 不同，TFS 分支存在于“路径空间”中。因此，您可以签入您的“外部”并为您想要引用的每个不同版本创建一个分支。然后，您可以配置工作区以从相应的分支路径引用适当的版本。或者，您可以考虑通过 NuGet 管理这些组件，设置私有 NuGet 源（可以像 UNC 路径一样简单）。
Unlike Subversion, TFS branches exist in "path space." So, you could check in your "externals" and create a branch for each distinct version of them you want to reference. Then, you can configure your workspace to reference the appropriate version from the corresponding branch path. Alternatively, you could consider managing these components via NuGet, setting up a private NuGet feed (can be as simple as a UNC path).