CODEWITHSUNDEEP
tfsbranch
user1437872
user1437872

Reputation: 45

TFS: How to maintain project references when branching

Our Visual Studio 2010 Solution includes six projects. One of the six is the main application and the remaining five are class libraries that are configured as Project References in the main application. Our TFS Source Control structure is as follows:

I need to create a Branch of Application1 so I have this:

My question is, when I create the Branch for Application1, do I also need to create Branches for the five Project References whether they get updated with the new feature or not? If I do, do I need to manually update the Project References so Application1-NewFeature knows to reference Class1-NewFeature instead of just Class1? When I merge the new feature back into the main branch, do I need to update the Project References all over again? Branching is totally new to me and I'm afraid I'll have a mess of Branches and Project References that gets out of control. What is "Best Practice" for this scenario?

Upvotes: 2

Views: 2201

Answers (1)

John Saunders
John Saunders

Reputation: 161773

I find it best, in effect, to branch the entire solution or system of solutions. It doesn't duplicate files, so it's not a big deal to have projects in your branch that you're not going to change.

Ironically, one rule of thumb that I use is that anything referenced via project references should be branched together.

Upvotes: 2

Related Questions