Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am currently using Tortoise SVN and a SVN plugin from my IDE.
Sometime problems appear, and it seems that my .svn aren’t always in a consistent state.
So is a bad practice to use two SVN clients ? (looking from a practical approach).
Do you have links related to SVN best practices ?
Thank you.
You can use however many makes it easy to do your job.
We’re using Tortoise on all machines, and AnkhSvn for those who use Visual Studio as well. Most of the time I’ll use the plugin, but it often has issues doing things like complicated moves or renames, so in those instances I’ll use Tortoise. Whatever gets the job done. I also really like the shell integration that Tortoise gives you.
If you’re using multiple clients, it’s a bit of trial and error to find which client works best for which operations, but that shouldn’t take too long.
One thing you need to watch is to make sure the SVN clients remain compatible with the version of SVN on your server, and that all the clients are capable of reading/writing between each other. I recommend reading the release notes before installing any updates to the clients (which often have automatic update type mechanisms).