Search code examples
visual-studio-2010svnsvn-trunk

Is it a good idea to maintain a "trunk" VS project folder in addition to folder(s) for branches?

In using Visual Studio 2010 on PC clients in an SVN environment, is it reasonable to assume that each project really needs a "trunk" reference working copy in addition to any branches that may be in use? I don't see how a single, branch copy without a trunk could ever be properly reconciled back to the repository when merging branch changes back to trunk...

Solution

  • Correct you need for every project (folder in the svn repsoitory) the default structure 

      Project
    +-- trunk
    +-- tags
    +-- branches