SharpDevelop Community

Hello, I used to use SD for all of my development. I recently tried out VS2008 and began to miss the SVN and NUnit integration.

I recently tried the Ankh SVN plugin for VS and accidentally opened some of my stuff with VS and AnkhSVN.  The version of AnkhSVN that works with VS2008 uses version 1.5 of SVN, now I'm getting errors saying my version of subversion is too old to work with the files, and I can't update or commit, and I've been forced to completely remove the VS integration and re-checkout all my files and copy changes over so that I can use my installed TortoiseSVN again.

 Is there any way in SD3.0 to define the version of SVN to use, or point it to the appropriate SVN executable so that I can upgrade to the latest SVN?  Or is there any plan to upgrade 3.0 to use the latest version of SVN, which is backward compatible with the current version?  I'd personally prefer the configurable option, so that I could upgrade at will w/out interfering with the integration.  I understand, however, that this solution is difficult and potentially impossible, given the possible API changes of the future.

SharpDevelop 2.2 ships with SVN 1.4 support, the current SharpDevelop 3.0 binaries use SVN 1.5.

Chris

 I don't mean to be contrarian.  I don't think I was all that clear, I was using the SVN integration in SD to do my commits for the orrigional message and for this one.

I was just using SD last night on a project, I have 1.4.7 Tortoise on my machine, and after some coding when I tried to commit it gave me the same message.  Could it be possible that some parts of the SVN integration use 1.5, and others are still on older?  Because I added a gui project to my solution last night, and other than reading the svn tags for modification, that's all I did.

 I'm using SD 3.0.0.3278... I've used nothing but SD on this particular project for the past week, and it's given me this message at least 3 times.

it just seems wierd that every time I try and do anything it keeps telling my my version is too old... I ended up renaming my project folder, checking out again, and copying changes over and re-adding the new files to the SVN.  It's very cumbersome to have to do this every time.  

If you use SharpDevelop 2.x, you must use TortoiseSVN 1.4.x.
If you use SharpDevelop 3.x, you must use TortoiseSVN 1.5.x.

 3.0.0 2970 is throwing the same error with:

TortoiseSVN 1.5.2, Build 13595 - 32 Bit

 Subversion 1.5.1

 "This client is too old to work with working copy"

Shukaido:

I'm using SD 3.0.0.3278...

I only bring out this quote because I'm already using a newer version, and still getting the error. 

This error can come from two sources:

1) The SVN library included in SharpDevelop is too old. (solution: use a recent SharpDevelop 3.0 version from the build server)

2) The TortoiseSVN client is too old (solution: use TortoiseSVN 1.5)

This is my big problem, I am using a relatively recent version, points to the previous post with the version/build number, and I didn't/don't use tortoise when I develop in SD3.  this issue happened most recently when I added a project through SD, and then tried to commit said project.  ALL IN SD3 version/build as specified in the previous post.

I have just installed the latest of the builds I could get as of yesterday, so I will update you when I do more with it.  In any case, this isn't a simple issue of conflicting tortoise and SD versions anymore, the last time it happened there was no TortoiseSVN involved at all, it was all SD.  I had to use TortoiseSVN to fix it, and get my new stuff commited, but the problem occurred in SD itself completely independent of my TortoiseSVN.

So, unless there is some sort of dependency on TortoiseSVN in SD, I don't think my lower version of Tortoise should effect SDs ability to commit a project that was entirely created, added, modified, and attempted to commit inside of SD.

SharpDevelop uses its own copy of the subversion library for marking files as added/removed/etc. This can upgrade the working copy to the 1.5 format.

However, SharpDevelop does not have it's own commit dialog - we simply start TortoiseSVN.

So there are two subversion libraries used by SharpDevelop: the one we ship for local operations, and the one shipped with TortoiseSVN for commit etc. Because the subversion 1.4 library cannot read working copies touched by the 1.5 library, you run into this kind of problem when either TortoiseSVN or SharpDevelop is too old.

Thank you, this explains the situation.  I didn't realize there was a dependency on Tortoise in SD...

[EDIT]: now that I review some of the previous posts, I missed one that says SD 3 requires TortoiseSVN 1.5.  Thank you for all your help and patience.