I currently use AnkhSVN to integrate subversion into Visual Studio. Is there any reason I should switch to VisualSVN?
AnkhSVN is free (in more than one sense of the word) while VisualSVN costs $50. So right there unless I'm missing some great feature of VisualSVN I don't see any reason to switch.
I used VisualSVN until Ankh hit 2.0, and ever since, I've abandoned VisualSVN. Ankh has surpassed VisualSVN in functionality, in my mind, and all the 1.x perf and integration issues are gone.
@Brad, have you used VisualSVN 1.5? It came out about a month ago as I recall, and it was a fairly major upgrade to my eye at least.
Not questioning your judgment here, just making sure you're comparing apples to apples.
@Jeff, Bloody hell, what's the time out there right now? Get some sleep!
@thelsdj, I used to really miss the integration when I switched to Tortoise SVN and now when I use TFS at work, it actually gets on my nerves. Maybe try that. I used to pooh pooh anything that didn't have integration, I thought I couldn't or wouldn't live without it.
@Ian, I also use Tortoise, but its nice to be able to quickly update or commit without having to go find stuff in the file manager.
I just upgraded my Ankh from 1.x to the new 2.0, looking good so far, though it didn't seem to pick up my C++ project (I mostly work with C# though, so not a deal breaker)
Not questioning your judgment here, just making sure you're comparing apples to apples.
So has anyone here actually tried both the 1.5 version of VisualSVN and the 2.0 version of AnkhSVN? I use VisualSVN at home and would love to use it at work, but they won't pay for it, so I'm really tempted to just buy the license myself...but if the new AnkhSVN is comparable (or better) then I'll just switch to that.
The main thing is that VisualSVN uses TortoiseSVN for nearly all of its UI. So you only really have to set up one client (preferred diff viewer, etc), and you can take advantage of things like the same "Previous messages" button on the Commit dialog, whether you're committing from Explorer or Visual Studio.
I had issues similar to Michael with AnkhSVN, but I'm using VS2008, that may be causing the problem.
For me, VisualSVN is pretty, but useless. AnkhSvn on the other hand, after it came in v2 as an scc provider, it works very good. VisualSVN tries to think for you, which is not an good thing, the user should be the controller, not the software.
Here is a funny story: I managed to corrupt one SVN repository with AnkhSVN last year. All I did was moving around the files. Thanks AnkhSVN!
I've been sticking with TortoiseSVN ever since. :)