Branching in TFS 2010 Part V (Sharing Code)

Branching
in
TFS 2010

Part V
by John Varan

Branching in TFS 2010: Part V
Sharing Common Code

Several Options
• Share source code as projects
• Manually copy assemblies
• Branching

Sharing Source Code

• Multiple versions are too hard to
manage
• Allows access to source to all
developers
• Increases build times of all projects

Manually Copying Assemblies

• Multiple versions easier to manage
• Restricts access to source code
• Build times are not affected
• No tracking or auditing

Branching Assemblies

• All advantages of manually
copying
• TFS provides tracking and auditing
• TFS provides ability to rollback
• Slightly more complicated (if new
to branching)

Setting it Up:

• Need a “Deploy” folder in common
library project
• Built assembly goes in here for
each release
• This can be automated

Folder Structure of Shared Library

Automating the “Deploy” folder:

• Post-build event to copy output
assembly to “Deploy” folder
• Existing assembly might be read-
only
• Pre-build event to check out
assembly

Pre-Build Event

Post-Build Event

Set Up of Referencing Application

Needs a “Lib” folder. Two Options:

• One for entire solution
• One for each project

Per Solution

• Easier
• No duplicates per project
• Can only have one version per
solution

Per Project

• Duplicates per project
• Slightly more complicated
• Can have different versions
mixed in solution

Sharing the Assembly

• Pick a specific release branch
• Open the “Deploy” folder
• Branch the actual .dll file to
another project’s “Lib” folder

Sharing the Assembly

End of Part V

Branching in TFS 2010 Part V (Sharing Code)

More Related Content

Similar to Branching in TFS 2010 Part V (Sharing Code) (20)

Recently uploaded (20)

Branching in TFS 2010 Part V (Sharing Code)