AnkhSVN和VisualSVN [英] AnkhSVN vs VisualSVN

问题描述

我们正在考虑在工作中改用SVN，因此我想知道VS2008(以及2010年推出时)的SVN插件.经过一番研究，我发现了AnkhSVN和VisualSVN，这两个似乎是最主要的. (我知道TortoiseSVN，并将与该插件结合使用).

We're thinking of switching to SVN at my work, so I was wondering about SVN plugins for VS2008 (and 2010 when it comes out). After a bit of research I found AnkhSVN and VisualSVN, the 2 that seemed most dominant. (I am aware of TortoiseSVN and will use the plugin in conjunction with it).

我知道这已经被提出了

I am aware that this has been asked before, but these questions were asked almost a year ago and we all know that a lot of things can change in a year.

问题:从您的经验来看，哪个更好，为什么?

推荐答案

当然，自从我逐一使用每种产品已经一年了，但是我目前的偏好是AnkhSVN.尽管人们对AnkhSVN的早期版本感到不满，但2.0几乎是对原始版本的重写，现在是完整的源代码管理提供程序集成包，而不是Visual Studio加载项.有了CollabNet的商业支持和开放的开源热情，AnkhSVN 2.0应该是一个机会.

Granted, it has been a year since I've used each product head-to-head, but my current preference is AnkhSVN. Though folks grumbled about early versions of AnkhSVN, 2.0 was a near rewrite of the original and is now a full Source Control Provider Integration Package rather than a Visual Studio Add-In. With commercial backing from CollabNet and renewed open source enthusiasm, AnkhSVN 2.0 deserves a chance.

我对AnkhSVN的两个最喜欢的功能是免费，我喜欢Pending Changes窗口.

My two favorite features of AnkhSVN are it is free and I love the Pending Changes window.

对于VisualSVN，我发现它很慢，我觉得它利用了TortoiseSVN，而不是过于频繁地处理文件管理本身.而且要花钱(虽然是少量的).

As for VisualSVN, I find it to be sluggish and I feel it leverages TortoiseSVN rather than handling the file management itself far too often. And it costs money (albeit a small amount.)

同样，这是基于我大约一年前的最后一次面对面测试.如前所述，TortoiseSVN本身很不错，但是如果您真的想插入VS IDE，请在VisualSVN之前先给AnkhSVN旋转一下.祝你好运.

Again, this is based on my last head-to-head test which was about 1 year ago. As already stated, TortoiseSVN is great on it's own, but if you really want to plug into the VS IDE, give AnkhSVN a whirl before VisualSVN. Best of luck.

这篇关于AnkhSVN和VisualSVN的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！