I've used AnkhSVN for the past year and I've never had a problem with it. I switch between that and TFS and some of the times I think I prefer AnkhSVN to TFS.
Early versions (1.X) of AnkhSVN were pretty unstable. Latest builds (v2.0.x) work as a native VisualStudio source control provider and it's very stable. I would recommend you to just download and try it yourself.
I also use AnkhSVN and it does work OK but I tend to drop to the file system to work with TortoiseSVN. For some reason I feel safer using Tortoise. I think that come's from concerns about Visual Studio than it is AnkhSsvn.
I tried AnkhSVN, but didn't like it. It tried to do too many things automatically and behind the scenes (e.g. adding files to SVN). I prefer if I see exactly what happens.
Now I mainly use TortoiseSVN (outside Visual Studio) or sometimes Mindscape VS FileExplorer in Visual Studio (which is available for free).
Note: VS FileExplorer plugin simply displays a file explorer in VS and allows you to invoke TortoiseSVN from there (and it also displays the TortoiseSVN overlay icons).
Update:
I reinstalled the current version of AnkhSVN 2.0.5250 and tried to reproduce the problems described above in a sample solution.
Result: AnkhSVN did exactly what I expected. I was not able to reproduce any of the problems. I think it might be time to give AnkhSVN another try at work!
Update 2:
I have now used AnkhSVN for some days, and I have to say it works very well. It's a big improvement compared to the previous version (1.x).
I use AnkhSVN and haven't had any issues worth complaining about. Sometimes (about 1 in 10 times?) I do get a strange nondescript error trying to commit, but restarting VS has always fixed the problem.
Edit: The error actually seems to be coming from the dataset designer, not AnkhSVN. Sometimes I get an error where it tries to "read or write to protected memory", which then just continues until I restart VS. Sorry for the confusion.
I have used both AnkhSVN and VisualSVN each for about 6 months. I prefer VisualSVN for one reason alone: Compatibility.
At my work, we keep our Subversion server and TortoiseSVN software very up-to-date (some people just go with one version and stick with it for years, but that's not our style). With new versions sometimes comes new working copy formats and it seems that AnkhSVN is very slow to adapt these new formats. What happens at this point is AnkhSVN completely breaks:
All the source files appear as "Added" even though they are all committed.
We are no longer able to Commit. An error appears claiming it does not recognize the new format.
VisualSVN has been "on the ball" in this respect as we have never had any compatibility issues with their software. This factor alone easily swayed me toward VisualSVN.
Another vote for visual SVN. To be honest, I think its just me being lazy. I could do everything visual svn does with just using tortoise, but it saves me from switching between programs. The color coded warning lights you get with visual svn are nice, but not that big a deal.
I use VisualSvn and it's fine. It wasn't expensive and it helps make sure you include all files you've added to the solution. It's not so good when using locking in svn (but then svn isn't great at locking files). If you want to edit a file that has needs-lock set, it will automatically update it when you lock it (sensible), but that could end up doing an update when you dont want it too.
I've got into trying Svn Monitor too and am happy with that, but it does seem to grind my computer to a halt.
I've tried old versions of ANKH but got in a mess and corrupted the svn repository (I suspect that was version 1.x) so I'd guess later versions are better.
I use VisualSVN, and love it. It may not be free but I found it extremely reliable, very well integrated, and very much worth the $49 per license. By setting up a few key-bindings comitting and updating become almost second-nature to my entire team (most of whom had no previous SVN/SCC experience).
Being able to quickly scan the solution explorer to see which files had changed was very useful for keeping tabs on things for writing status reports and the like (but that's probably specific to my overly beurocratic manager).
The "Checkout Solution from SVN" feature was great for quickly getting the summer student interns setup and giving them a gentle introduction to version control. Again, this is probably specific to our needs so may not be of interest to you.
So a thumbs-up for VisualSVN and the convenience it gives us.
My experience with working with AnkhSVN is better than tortoise but it still has a lot of flaws that you really don't get with native Visual Studio plugins like Source Safe, TFS, Dynamic soft. It has real problems with the .svn folders and synchronising so you end up spending a portion of your time removing the .svn folder and starting again.
That's my experience. One example is moving a folder from one project (in the same solution) to another project. It breaks on this from the working set being different. The solution is to go into the folder and remove the .svn files but it seems like a a lot of effort.
I'm use to it being a mirror of my filesystem though, and basic 2 developer branches of files.
发布评论
评论（14）
我去年使用 AnkhSVN，从来没有遇到过任何问题。 我在 TFS 和 AnkhSVN 之间切换，有时我想我更喜欢 AnkhSVN 而不是 TFS。
I've used AnkhSVN for the past year and I've never had a problem with it. I switch between that and TFS and some of the times I think I prefer AnkhSVN to TFS.
我使用 VisualSVN，它运行得很好，但你是对的，它不是免费的。 这里没有 Ankh 的经验。
I use VisualSVN and it works great, but you're correct, it's not free. No experience with Ankh here.
AnkhSVN 的早期版本 (1.X) 非常不稳定。 最新版本 (v2.0.x)作为本机 VisualStudio 源代码控制提供程序，它非常稳定。 我建议您下载并亲自尝试。
Early versions (1.X) of AnkhSVN were pretty unstable. Latest builds (v2.0.x) work as a native VisualStudio source control provider and it's very stable. I would recommend you to just download and try it yourself.
我也使用 AnkhSVN，它工作正常，但我倾向于使用文件系统来使用 TortoiseSVN。 出于某种原因，我觉得使用 Tortoise 更安全。 我认为这是出于对 Visual Studio 的担忧，而不是 AnkhSsvn。
I also use AnkhSVN and it does work OK but I tend to drop to the file system to work with TortoiseSVN. For some reason I feel safer using Tortoise. I think that come's from concerns about Visual Studio than it is AnkhSsvn.
我尝试过 AnkhSVN，但不喜欢它。 它试图在幕后自动执行太多操作（例如，将文件添加到 SVN）。 我更愿意看到到底发生了什么。
现在我主要使用TortoiseSVN（在Visual Studio之外）或者有时Mindscape VS FileExplorer 在 Visual Studio（免费提供）中。
注意：VS FileExplorer 插件仅在 VS 中显示一个文件资源管理器，并允许您从那里调用 TortoiseSVN（并且它还显示 TortoiseSVN 覆盖图标）。
更新：
我重新安装了当前版本的 AnkhSVN 2.0.5250，并尝试在示例解决方案中重现上述问题。
结果：AnkhSVN 完全符合我的预期。 我无法重现任何问题。 我想也许是时候再一次尝试 AnkhSVN 了！
更新2：
我现在已经使用AnkhSVN一些天了，我不得不说它效果非常好。 与之前的版本（1.x）相比，这是一个很大的改进。
I tried AnkhSVN, but didn't like it. It tried to do too many things automatically and behind the scenes (e.g. adding files to SVN). I prefer if I see exactly what happens.
Now I mainly use TortoiseSVN (outside Visual Studio) or sometimes Mindscape VS FileExplorer in Visual Studio (which is available for free).
Note: VS FileExplorer plugin simply displays a file explorer in VS and allows you to invoke TortoiseSVN from there (and it also displays the TortoiseSVN overlay icons).
Update:
I reinstalled the current version of AnkhSVN 2.0.5250 and tried to reproduce the problems described above in a sample solution.
Result: AnkhSVN did exactly what I expected. I was not able to reproduce any of the problems. I think it might be time to give AnkhSVN another try at work!
Update 2:
I have now used AnkhSVN for some days, and I have to say it works very well. It's a big improvement compared to the previous version (1.x).
我使用 AnkhSVN 并且没有遇到任何值得抱怨的问题。 有时（大约十分之一？）我在尝试提交时确实遇到了一个奇怪的、不伦不类的错误，但重新启动 VS 总是能解决问题。
编辑：错误实际上似乎来自数据集设计者，而不是 AnkhSVN。 有时我会收到一个错误，它尝试“读取或写入受保护的内存”，然后该错误会一直持续到我重新启动 VS。 对困惑感到抱歉。
I use AnkhSVN and haven't had any issues worth complaining about. Sometimes (about 1 in 10 times?) I do get a strange nondescript error trying to commit, but restarting VS has always fixed the problem.
Edit: The error actually seems to be coming from the dataset designer, not AnkhSVN. Sometimes I get an error where it tries to "read or write to protected memory", which then just continues until I restart VS. Sorry for the confusion.
我已经使用 AnkhSVN 和 VisualSVN 大约 6 个月了。 我更喜欢 VisualSVN 的原因只有一个：兼容性。
在我的工作中，我们保持 Subversion 服务器和 TortoiseSVN 软件处于最新状态（有些人只使用一个版本并坚持使用多年，但这不是我们的风格）。 新版本有时会带来新的工作副本格式，AnkhSVN 适应这些新格式的速度似乎非常慢。 此时发生的情况是 AnkhSVN 完全崩溃：
VisualSVN 在这方面一直“敏锐”，因为我们从未与他们的软件发生过任何兼容性问题。 仅这个因素就很容易让我转向 VisualSVN。
I have used both AnkhSVN and VisualSVN each for about 6 months. I prefer VisualSVN for one reason alone: Compatibility.
At my work, we keep our Subversion server and TortoiseSVN software very up-to-date (some people just go with one version and stick with it for years, but that's not our style). With new versions sometimes comes new working copy formats and it seems that AnkhSVN is very slow to adapt these new formats. What happens at this point is AnkhSVN completely breaks:
VisualSVN has been "on the ball" in this respect as we have never had any compatibility issues with their software. This factor alone easily swayed me toward VisualSVN.
Agent SVN 插件在集成 Subversion 和 Visual Studio 方面做得很好，但它也不是免费的。
The Agent SVN plug-in does a good job of integrating Subversion and Visual Studio, but it too is not free.
又一票投给了视觉SVN。 说实话，我觉得只是我懒而已。 我可以只使用 tortoise 完成 Visual svn 所做的一切，但它使我免于在程序之间切换。 通过 Visual svn 获得的颜色编码警告灯很不错，但没什么大不了的。
Another vote for visual SVN. To be honest, I think its just me being lazy. I could do everything visual svn does with just using tortoise, but it saves me from switching between programs. The color coded warning lights you get with visual svn are nice, but not that big a deal.
我用的是VisualSvn，没问题。 它并不昂贵，并且有助于确保您包含已添加到解决方案中的所有文件。 在 svn 中使用锁定时不太好（但是 svn 不擅长锁定文件）。 如果你想编辑一个设置了需求锁定的文件，当你锁定它时它会自动更新它（明智的），但是当你也不想要它时，这可能最终会进行更新。
我也开始尝试 Svn Monitor 并且对此感到满意，但它似乎确实让我的电脑停止运转。
我尝试过旧版本的 ANKH，但陷入混乱并损坏了 svn 存储库（我怀疑那是版本 1.x），所以我猜更高的版本会更好。
I use VisualSvn and it's fine. It wasn't expensive and it helps make sure you include all files you've added to the solution. It's not so good when using locking in svn (but then svn isn't great at locking files). If you want to edit a file that has needs-lock set, it will automatically update it when you lock it (sensible), but that could end up doing an update when you dont want it too.
I've got into trying Svn Monitor too and am happy with that, but it does seem to grind my computer to a halt.
I've tried old versions of ANKH but got in a mess and corrupted the svn repository (I suspect that was version 1.x) so I'd guess later versions are better.
我使用 VisualSVN，并且喜欢它。 它可能不是免费的，但我发现它非常可靠，集成得很好，并且非常值得每个许可证 49 美元。 通过设置一些键绑定，提交和更新几乎成为我整个团队的第二天性（他们中的大多数人以前没有 SVN/SCC 经验）。
能够快速扫描解决方案资源管理器以查看哪些文件已更改对于密切关注编写状态报告等内容非常有用（但这可能是我过于官僚化的经理所特有的）。
“SVN 的结帐解决方案”功能非常适合快速让暑期学生实习生进行设置，并向他们简要介绍版本控制。 同样，这可能是针对我们的需求的，因此您可能不感兴趣。
所以对 VisualSVN 及其给我们带来的便利点赞。
I use VisualSVN, and love it. It may not be free but I found it extremely reliable, very well integrated, and very much worth the $49 per license. By setting up a few key-bindings comitting and updating become almost second-nature to my entire team (most of whom had no previous SVN/SCC experience).
Being able to quickly scan the solution explorer to see which files had changed was very useful for keeping tabs on things for writing status reports and the like (but that's probably specific to my overly beurocratic manager).
The "Checkout Solution from SVN" feature was great for quickly getting the summer student interns setup and giving them a gentle introduction to version control. Again, this is probably specific to our needs so may not be of interest to you.
So a thumbs-up for VisualSVN and the convenience it gives us.
我使用 AnkhSVN 的经验比乌龟更好，但它仍然有很多缺陷，这些缺陷是使用本机 Visual Studio 插件（例如 Source Safe、TFS、Dynamic soft）确实无法得到的。 它在 .svn 文件夹和同步方面存在真正的问题，因此您最终会花费一部分时间删除 .svn 文件夹并重新开始。
这就是我的经验。 一个示例是将文件夹从一个项目（在同一解决方案中）移动到另一个项目。 它打破了这一点，因为工作集不同。 解决方案是进入该文件夹并删除 .svn 文件，但这似乎需要付出很大的努力。
不过，我习惯了它作为我的文件系统的镜像，以及文件的基本 2 个开发人员分支。
My experience with working with AnkhSVN is better than tortoise but it still has a lot of flaws that you really don't get with native Visual Studio plugins like Source Safe, TFS, Dynamic soft. It has real problems with the .svn folders and synchronising so you end up spending a portion of your time removing the .svn folder and starting again.
That's my experience. One example is moving a folder from one project (in the same solution) to another project. It breaks on this from the working set being different. The solution is to go into the folder and remove the .svn files but it seems like a a lot of effort.
I'm use to it being a mirror of my filesystem though, and basic 2 developer branches of files.
AnkhSVN 插件还不错。
The AnkhSVN plug-in is not too bad.
我使用 vsTortoise。
它工作得非常好，特别是当您熟悉 TortoiseSVN 并且它是免费的时。
I use vsTortoise.
It works very nice especially when you are familiar with TortoiseSVN and it's free.