What do you like and dislike with the latest Version Control guidance?


We are investigating the next phase of the Version Control (ex Branching and Merging) Guidance, potential integration with MSDN, using other delivery channels and accepting contributions from the ALM community.

current portfolio

We would appreciate if you could review the latest guidance and give us candid feedback on content and delivery format.

If you could pin  image  three (3) features on our backlog, what would they be?

please share candid feedback

We can’t wait to hear from you. Here are some ways to connect with us:

  • Add a comment below.
  • Contact us on our blog.
Comments (5)
  1. willys says:

    Would you, for example, prefer the guidance to move to a crisper markdown style, as in the case of github.com/…/Extracting-effective-permissions-from-TFS, allowing you to submit content changes?

  2. Om says:

    Could you please guidance on how to contain the growth of "Tbl_Content". This table grows to hundreds of GBs for source code under which is under 1 GB? It's growth doesn't seem legit.

  3. Om Prakash says:

    Dealing with large code base having 10000+ files in workspace. Source control explorer and solution explorer lock on local workspace (TF400030). This renders visual studio unworkable. More than guidance product fix is required.

  4. @Om, what type of data are you storing in source control? Tbl_content growth could be legit even for a small repo, especially if there binary or other content that does not deltify well, and if there are a lot of versions.

  5. @Om Prakash, what issues are you dealing with. Based on Dogfooding and feedback from the team local workspaces only have issues above 100,000 items (approximately) – 10,000 items should work fine on modern hardware.  If you have a very large workspace, the guidance is to use server workspaces to improve performance.

    Also see http://blogs.msdn.com/b/willy-peter_schaub/archive/2011/11/30/team-foundation-server-trying-to-understand-server-versus-local-workspaces.aspx.

Comments are closed.

Skip to main content