We use TortoiseSVN + VisualSVN and we have a system we'd like to get under version control, and I'm trying to figure out the best way to set it up. Unfortunately code edits do occur directly in the production environment (I'd like to move away from this practice but it would require some major system changes so it's not something I can change today) so I need to consider the production code base as a working copy and multiple users need to be able to commit to the repository from that working copy. How do I set it up so that multiple users to share a working copy?
Users login information is stored in the .svn folders so I get an error when a different users attempts to commit a change using a working copy that I checked out. On an older version of subversion (several years ago) I was using svn+ssh and I was able to remove user specific information from the svn+ssh command so that it worked for anyone (since each user had auto-username set in putty). But now I see that subversion uses a non-text format so I can't remove information of the user that checked it out.
Although I have a preference for subversion (our users already know it) I'd be open to hear if a similar setup is possible or would work better on alternative solutions (git, mercurial, etc.) as long as there is a plugin for Visual Studio similar to VisualSVN.