SharpSVN package with SASL support
Hi folks,
I hope 2025 will be a better year for all of us!
I'm using SharpSVN to build my own SVN Client on Windows. I'm using Nuget on C# to get the package. However, I'm unable to connect to any server that uses SASL for user authentication.
After performing reverse engineering on SharpSVN.dll, I couldn't find any references or links related to SASL within the DLL.
Am I missing something? If so, could you guide me on how to enable SASL support? Do I need to download additional components separately? Is there any documentation or a prebuilt package with SASL support available?
Thanks ~ devnull
I'm not sure about the very last versions where we had to convert some scripts to use more git and less subversion to obtain dependencies, but before that SharpSvn imported cyrus sasl for authentication using the svn:// protocol. Subversion doesn't support sasl authentication for http(s):// connections.
Most of this is in in the nant scripts in the imports directory.
Thanks, I understood. I consider SASL authentication for the svn:// protocol to be quite common, as few people use the svn:// protocol with plain-text authentication.
Would you find it interesting to enable SASL in the default SharpSVN package via NuGet? I believe it would be quite useful for most users who use the svn:// protocol.
I haven't built SharpSvn for some time. I will see what I can do. It used to be enabled, but there is some bitrot in the patches.
I mostly use git these days, but I working to get a few things upgraded in the scripts (and build against more recent Subversion and Openssl, etc.) Everything can be built on github using these scripts so some help to get things integrated would be very useful.
The last few releases were build through a group of users that still actively uses SharpSvn, but has a limited set of users. So they might not be interested in keeping all scenarios supported. (Just don't know). Patches to this repository always welcome
@rhuijben
Thanks for your reply, I very appreciate. I understood.
I even followed the instructions and the script, and I managed to build the DLLs with some technical adjustments. However, the script generated several DLLs for me, not just one as is usually the case with the package obtained via NuGet, and I had trouble understanding how to integrate all of them into my project.
I'm a *nix user, so I was a bit lost on how to integrate all of them (dlls) in Visual Studio or integrate all of them in a single dll.