One strategy could be to put the shared code in one of the 2 repositories (or in a 3rd repository), and have the other developer check out that code "separately". You also might want to have a look at the svn:externals property (http://svnbook.red-bean.com/en/1.5/ svn.advanced.externals.html).
However, from experience I would advise against sharing at code level. If at all possible, a preferable approach would be to set up the sharing at binary level. (I.e, maintain the shared code as a separate project, and share the artifacts of that project.) Obviously this approach is not always practical, but working with svn:externals can also be a pain. good luck, jeroen On 21 jan, 23:56, [email protected] wrote: > Situation: I have two programers working in two separate > repositories. There are common files (code) that both programers use > and modify. Both programers must use the same common files at all > times even if one or the other has made changes. They are using > VisualSVN Server and TortoiseSVN Clients.
