Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > .NET > .NET 4 and Visual Studio 2010 > BOOK: Professional Team Foundation Server 2010
Password Reminder
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Professional Team Foundation Server 2010
This is the forum to discuss the Wrox book Professional Team Foundation Server 2010 by Ed Blankenship, Martin Woodward, Grant Holliday, Brian Keller; ISBN: 978-0-470-94332-8
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional Team Foundation Server 2010 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Display Modes
  #1 (permalink)  
Old January 31st, 2012, 09:25 PM
Registered User
Points: 11, Level: 1
Points: 11, Level: 1 Points: 11, Level: 1 Points: 11, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Mar 2008
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default 3rd Party Dependencies - folder in branch question

on p 222 - 1st para suggests that an issue with this approach is the increased use of storage since "each product family set of branches contained in version control has a copy of dependencies."

But I thought that branches contained only 'pointers' to the files, p 190: "when you perform the branch, it doesn't actually create new copies .. it just creates a record pointing to them."

Please clarify if possible ASAP we are planning our tfs structure and space usage is a big concern (and we have quite a few 3rd party assemblies).

thx, riix
  #2 (permalink)  
Old January 31st, 2012, 09:54 PM
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.

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Where to obtain 3rd party components MichaelBate General .NET 1 August 29th, 2008 09:00 PM
3rd party application from ASP MehulCSC Classic ASP Basics 1 June 9th, 2008 02:18 PM
Favorite 3rd party software with MySQL MySQLGeek MySQL 0 January 11th, 2008 05:32 AM
Crystal and Oracle and 3rd Party narooma.12 Crystal Reports 0 January 4th, 2005 04:08 AM

All times are GMT -4. The time now is 05:52 AM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.