使用Visual Studio的源代码控制:从VisualSVN切换到Ankh? [英] Source Control with Visual Studio: switch from VisualSVN to Ankh?

问题描述

我正在为我和一小组开发人员评估VisualSVN.我将其毫无问题地设置在服务器(VisualSVN服务器)上，并安装了TortoiseSVN和VisualSVN以便将其集成到Visual Studio 2008中.到目前为止，它运行良好，我们将其用于主要应用程序的开发.

I am evaluating VisualSVN for me and a small team of developers. I set it up on the server (VisualSVN server) without problems and installed TortoiseSVN and VisualSVN in order to integrate it in Visual Studio 2008. So far, it works well and we use it for the development of our main application.

我也听说过有关AnkhSVN新版本的好消息，该版本是开源的且免费的.由于我们刚开始使用Subversion，所以我现在要做出正确的决定.

I've heard good things about the new version of AnkhSVN too, which is open source and free. Since we are at the beginning with Subversion, I want to make the right decision now.

是否可以轻松地从VisualSVN切换到AnkhSVN ?我可以保留VisualSVN Server的安装，还是也必须切换安装?如果我开始使用AnkhSVN，TortoiseSVN是否已过时?而且，当前版本在Visual Studio 2008中是否可靠?

Is it possible to switch from VisualSVN to AnkhSVN without too many hassles? Can I keep the VisualSVN Server installation or do I have to switch that too? Is TortoiseSVN obsolete if I start using AnkhSVN? And, is the current version reliable in Visual Studio 2008?

要明确:每位开发人员的费用约为50美元.这是为未来做出正确的决定.您有什么建议?

To be clear: it's not about the 50 US$ per developer. It's about making the right decision for the future. What do you recommend?

非常感谢！

推荐答案

我们正是这样做的:从VisualSVN切换到AnkhSVN.此举完全没有任何麻烦.这些插件不存储特定信息，并且.svn(或_svn)隐藏文件夹与任何svn客户端兼容.

We did precisely that: switched from VisualSVN to AnkhSVN. The move went without any trouble at all. These plugins do not store specific information, and the .svn (or _svn) hidden folders are compatible with any svn client.

Ankh插件的1.x系列非常糟糕:发生了很多崩溃和烦恼(例如，移动或重命名尚未提交的文件非常困难). 2.x系列解决了大多数问题，尽管它仍未达到VisualSVN的水平，但我发现它足以满足我们的使用要求(而且非常免费).

The 1.x series of the Ankh plugin was awful: lots of crashes and annoyances (for example, it was very hard to move or rename a not-still-commited file). The 2.x series corrects most of the problems, and while it still does not attains the level of VisualSVN, I found it very sufficient for our uses (and very free).

关于迁移本身，再简单不过了:我们只是卸载了VisualSVN，然后安装了Ankh.只要您的目录受源代码管理，它就可以工作.

About the migration in itself, it couldn't be more simple: we just uninstalled VisualSVN, and installed Ankh. As long as your directory is under source control, it works.

唯一的共同点是，您仍然需要TortoiseSVN来完成许多任务，无论是高级任务还是更基本的任务:创建工作目录和在资源管理器中检出比使用Visual Studio要简单得多.

The only common thing is that you still need TortoiseSVN to do many things, be them advanced tasks, or more basic ones: it's much simpler to create working directories and to checkout within explorer than with Visual Studio.

这篇关于使用Visual Studio的源代码控制:从VisualSVN切换到Ankh?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！