团队基础服务器 2012 中的 SVN 外部替代方案

本文介绍了团队基础服务器 2012 中的 SVN 外部替代方案的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

目前我们使用 SVN 进行源代码控制.由于开发环境中的额外功能和集成，我们希望迁移到 TFS 2012.

Currently we use SVN for our source control. Because of the extra features and integration in the development environment we would like to migrate to TFS 2012.

我们有很多门户正在运行，它们是在 asp 中构建的.在我们的门户中，我们使用了许多标准组件.目前所有门户都使用相同的代码库.这意味着每当我们更改共享代码库中的某些内容时(无论何时发布门户)，它都会自动分发.我们非常习惯这种工作方式，我们知道在其他门户中存在破坏代码的风险.但是，在所有其他门户中发布更改将花费大量时间.为此，我们在 SVN 中使用外部组件.

We have a lot of portals running that are build in asp. Within our portal we use a lot of standard components. Currently all portals use the same code base. This means that whenever we change something in the shared codebase it is (whenever a portal is published) automatically distributed. We are very used to this way of working and we know there is a risk of breaking code in other portals. Though, publishing changes in all other portals would cost way to much time. So to do this we use externals in SVN.

我真的很想保持此功能正常运行.所以我的问题是，有没有办法在 SVN 中创建一个类似外部的系统，或者有没有一种非常好的方法可以有效地替换此功能.

I would really like to keep this functionality up and running. So my question is, is there a way to create a external like system in SVN or is there a realy good way that works just as efficient to replace this functionality.

推荐答案

Visual Studio 团队中有几个建议Foundation Server 分支和合并指南.

如果您下载Everything"包并查看All Guides"zip 并阅读Advanced Version Control Guide".

If you download the "Everything" package and look in "All Guides" zip and have a read of "Advanced Version Control Guide".

第 5-19 页(2.1 版)涵盖了管理共享资源，那里有很多内容，为 Stack Overflow 总结所有内容可能会对 Ranger 造成不公正，所以我只是指出.

Pages 5-19 (Version 2.1) cover Managing Shared Resources, there's a lot there and summarising it all for Stack Overflow will probably do the Ranger's an injustice, so I'll just point you there.