Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

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.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7073739
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T05:57:57+00:00 2026-05-28T05:57:57+00:00

I have the following directories in my Subversion repository for a Visual Studio solution:

  • 0

I have the following directories in my Subversion repository for a Visual Studio solution:

  • ProjectName
    • tags
    • branches
    • trunk
      • MySolution.sln
      • MyProject1 (dir)
      • MyProject2 (dir)

If I update MyProject1 from version 1.0.0 to 2.0.0, should I copy everything in trunk to a new directory under tags, or should I only copy everything in trunk/MyProject1 to a new directory under tags?

And, if the former is the correct way of doing things, how do I version an entire Visual Studio solution?

Thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T05:57:57+00:00Added an answer on May 28, 2026 at 5:57 am

    Take a look at the svn guide to understand basic versioning concepts.

    Trunk is the main line of development so you can update from version 1.0.0 to 1.0.1, 2.0.0 etc.

    Branch is a copy of your trunk to develop a feature or something else without affecting the Trunk. You can merge at any time the branch code to the trunk code or throw it away.

    Tag is a snapshot at a given time of your trunk o branch.

    In your case you can update from 1.0.0.0 to 2.0.0.0 in trunk and maybe keep a snapshot by tagging your 1.0.0.0 release (copying all trunk to a tag named 1.0.0.0).

    First you can checkout ProjectName to your local disk, for example c:\working\ProjectName.
    In this way you have this first local structure:

    • ProjectName
      • tags
      • branches
      • trunk
        • MySolution.sln
        • MyProject1 (dir)
        • MyProject2 (dir)

    When you reach your 1.0.0.0 release tag it to have this structure:

    • ProjectName
      • tags
        • 1.0.0.0
          • MySolution.sln
          • MyProject1 (dir)
          • MyProject2 (dir)
      • branches
      • trunk
        • MySolution.sln
        • MyProject1 (dir)
        • MyProject2 (dir)

    Then update to 2.0.0.0 and so on:

    • ProjectName
      • tags
        • 1.0.0.0
          • MySolution.sln
          • MyProject1 (dir)
          • MyProject2 (dir)
        • 2.0.0.0
          • MySolution.sln
          • MyProject1 (dir)
          • MyProject2 (dir)
      • branches
      • trunk
        • MySolution.sln
        • MyProject1 (dir)
        • MyProject2 (dir)

    At any time you can work on trunk or release 1 or 2 (maybe for debugging or applying patches)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a repository that has the following directories: branches tags trunk The trunk
I have the following problem using subversion: I'm currently working on the trunk of
CentOS 5.5 Subversion 1.4 httpd-2.2.3-43.el5.centos.3 I have the following repository structure I am created
i have the following directories: -UI -BusinessLogic -DataAccess -BusinessObjects if i have a class
I have the following program to browse all virtual directories and their sub directories
I have the following situation: multiple virtual directories under same application pool in IIS
I have the following directories structure: g1/ .git a b c/ .git d e
I have following files and directories in my project root directory main.py bar.py foo
I am experimenting with makefile...mainly when sources are in many directories I have following
Within my Subversion project I have a few directories that contain other open source

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.