问题描述
任何可用于从 .net 应用程序(使用 C#)访问 SVN 的 GOOD 库.到目前为止我发现的唯一 3 个我将尝试的是:
Any GOOD libraries available to access SVN from .net application (using C#). The only 3 I found so far that I will be trying out is:
我想创建一个非常简单的 SVN 客户端！
I want to create a very simple SVN client!
推荐答案
SharpSvn 是为 .Net 2.0 和 Subversion 1.5 及更高版本设计的.它将所有 subversion 依赖项集成在一组可直接从 .Net 使用的 dll 中(XCopy 可部署).SharpSvn 的其他优点之一是它隐藏了所有内存管理并在异常中转换 Subversion 错误，更重要的是反之亦然.(使调试回调变得非常容易)
SharpSvn was desiged for .Net 2.0 and Subversion 1.5 and later. It integrates all subversion dependencies in a single set of dll that is directly usable from .Net (XCopy deployable). One of the other strong points of SharpSvn is that it hides all memory management and transforms Subversion errors in exceptions, and more importantly vice versa. (Makes debugging callbacks very easy)
NSvn 在 AnkhSVN 2.0 之前被 AnkhSVN 使用.之后它转移到了 SharpSvn.
NSvn was used by AnkhSVN before AnkhSVN 2.0. It moved to SharpSvn after that.
Codeplex 上的 IronSvn 项目关闭了.(建议使用 SharpSvn).
The IronSvn project on Codeplex closed down. (It suggests using SharpSvn).
Svn# 及其 2.0 后继者 Svn.Net 是 Subversion C api 的简单包装.他们需要 subversion 版本的二进制文件才能工作.并且您必须管理 apr 池和一些从托管代码中自己编组的 apr 集合.这是此列表中唯一的跨平台解决方案.(在 linux 上也能正常工作)
Svn# and its 2.0 successor Svn.Net are plain wrappers of the Subversion C api. They required the binaries of a subversion release to work. And you must manage the apr pools and some of the apr collection marshalling yourself from managed code. This is the only cross platform solution in this list. (Works just as well on linux)
这篇关于我必须使用 SVN API 或库访问/提交/更新 WPF 应用程序中的 SVN 存储库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！