AnkhSVN versus VisualSVN [closed]

Answer 1

I recently tried Ankh but quickly switched back to VisualSVN. Because:

• Better commit dialog (use UI of tortoise)
• No refresh problems (which i had using ankh) Imho visual svn is easilty worth its money

Answer 2

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.

Answer 3

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.

Answer 4

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.