Subversion Integration Problem (crash)

[Thomas Bednarz]

I just updated my recently bought Version 7.0 to 7.1. For a new project I tried to integrate with subversion.

I use VisualSVN (Windows Server) and TortoiseSVN as client. When I try to configure EA to use SVN it simply hangs forever.

As Subversion Exe I added TortoiseProc.exe, since I do not have a SVN.exe. (My server is on the net)

Could anybody help me with that?

Many thanks.

Thomas

[Frank Horn]

Guess you'll need SVN.exe after all. You can simply download a windows setup from http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 and install it on your machine, I don't think it's ever done any harm.

[Thomas Bednarz]

Hi Frank,

Thanks, I did already install that. But it requires an Apache Web Server so I guessed this is a server install only. The setup did not offer me to do some sort of a client install only.

Any suggestions?

Many thanks.

Thomas

[Frank Horn]

Thomas,

I don't have Apache on my machine either and installed SVN all the same. It did not complain and it works perfectly as long as I don't do anything with it which requires a local web server. EA uses it as a local client, and I do the same when I get stuck with Tortoise and have the time to look up all those command line parameters. Due to lack of a complete .Net wrapper for SVN I once even used it (only experimentally, though) by starting it as a process in a C# application,  redirecting the standard output to a StringWriter and parsing the result.

Our repository is on some virtual server with Apache and Tortoise as well as my client side SVN.exe access it via WebDav. I think your confusion (and mine, back when we introduced SVN) originates from the fact that the SVN folks have put client and server functionality into one exe. It's compiled against Apache API, but as long as you don't use any server commands (like creating a local repository with WebDav access) the Apache API will never be called. And EA does nothing of this sort. It just calls client commands like locking, updating and committing, and passes the repository URL from the respective package's version control configuration. And this URL can point to anything an SVN client understands, like a local file based repository, a remote WebDav server or whatever.

Frank

[Thomas Bednarz]

Frank,

Thanks a lot for this interesting details. Very helpful at all!
Adding server and client in the same binary is sort of a special design !
I'll give that binary a try and hope it will not conflict with TortoiseSVN.

TortoiseSVN is a lot more stable then TortoiseCVS ever was! However I currently have to run 3 Version Control Systems: M$ VSS, CVS and new Subversion. Well after 15 years of coding, designing software etc. things summarize .....

What do you mean by a .NET wrapper? If you need a M$ VisualStudio Integration have a look at http://www.visualsvn.com/. I run their SVN Server and have nothing to complain so far.

Thomas

[Frank Horn]

AFAIK SVN command line application doesn't conflict with Tortoise. Never had any problems.

As to an SVN wrapper:  I didn't mean integration into Visual Studio, but an automation interface. There's  DotSVN (http://www.dotsvn.net/), which is only halfway complete. Meanwhile I've also found SubversionSharp (http://www.softec.st/en/OpenSource/ClrProjects/SubversionSharp/SubversionSharp.html), but I#ve not taken a closer look at this one so far.