Home/ Questions/Q 6909719
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T08:43:30+00:00

I have my TFS 2010 structure as follows: ProjectCollectionA ..trunk ….Dev (this is a

  • 0

I have my TFS 2010 structure as follows:

ProjectCollectionA
       ..trunk
            ....Dev (this is a branch) 
                  ...Website1(these are folders)
                  ...Website2

            ....Release(this is a branch)
                  ...Website1(these are folders)
                  ...Website2

For whatever reason, I have dev and release as Branches and Website1, Website2 as Folders. My question is should I be having dev and release as folders and Website1 and Website2 as branches? Does that make more sense? What is the best practice here? Any advantages or disadvantages going one way or other? Thanks for the help

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There’s a very comprehensive guide here from the ALM Rangers that explains the different branching practices in TFS.

    If Website 1 and Website 2 are related applications within the same overall solution (not VS solution) or if there are any dependencies between the two Websites, then this (IMO) is the best approach. If they are two completely unrelated projects with isolated code bases, I would seperate it into two TFS Projects.

    It’s hard to decide on a correct branching pattern for someone without knowing the full ins and outs of thier business practices. What we do here, might not work for you (Actually, what we do we probably shouldn’t).

    • 0