View Single Post
  #2 (permalink)  
Old January 31st, 2012, 09:54 PM
dkallen dkallen is offline
Registered User
Points: 9, Level: 1
Points: 9, Level: 1 Points: 9, Level: 1 Points: 9, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Sep 2011
Location: Minneapolis, Minnesota, USA
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default how TFS stores files in branches

You left out the nearby sentence that includes the word "potentially" as in
"This potentially can cause more data storage to be used"
The pointer argument still holds, protecting you from massive duplication of 3rd-party DLLs when you branch. But if you CHANGE lots of these files in one branch, then it must try to find a way to keep up with the differences.

I recommend Bill Heys' post on the subject

Unless you do some really weird things with your dependencies, I don't see you will have a problem. First, a sensible strategy for dependencies is to put them in folders with version numbers on them. So you would usually not change a file, but would simply add a new version from time to time. In my experience, we do not churn dependencies a great deal.

If you are still nervous after reading Bill's very authoritative (from the product team) post, just do a quick experiment and watch your database after adding 100 MB of DLLS and then branching.