Best Strategy for Branching SVN Code and Supporting Links to Visual Studio Projects

Question

We have the main visual studio project, stored in SVN, using the standard trunk / branch / tag structure. However, this project refers to external projects outside this structure, so when we create a code branch, all links to exteranl projects fail because they are at the same level.

i.e. trunk / MyProjectCode becomes branches / MyFeatureBranch / MyProjectCode after branching, and therefore, because of this extra level of hierarchy, any links to external projects fail.

What is the best approach for creating branches with minimal friction? I could write a script that changes all references to the project, or I could change my local code layout, so that the branches were actually level down from the trunk, so the new branch would be at the same level. Any other suggestions / recommendations?

Answer 1

When checking from Subversion, your working directory should not reflect the same directory depth as in the repository. Using the command line as an example:

svn co svn: // server / project / trunk project
svn co svn: // server / project / branches / MyFeatureBranch project-feature

, project project-feature. .

Answer 2

, . , 5 , , 5 , , , . , Junction.

Answer 3

, , , , , . () , ( C:\SharedLibs\Library\Version). sharedlib svn, SharedLibs .

, , - , : . . src ( ) lib ( ). , , : , ( ), .

- svn: externals. , ( ) . , , . svn: http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html

Answer 4

, .sln .csproj, . , VS - ( Dev , ).

" " : , , ?

:

C:
 |_ svnworkarea
       |_ project
           |_ branches
               |_ project-feature
                       |_ source etc

           |_ trunk
               |_ source etc

:

C:
 |_ svnworkarea
    |_ project
         |_ project-feature
               |_ source etc

         |_ trunk
               |_ source etc

, . - , , , . NewUIBranch.