CODEWITHSUNDEEP
visual-studiovisual-studio-2012tfs
dom_beau
dom_beau

Reputation: 2497

How to share binaries between development teams using VS2012 and TFS2012

We are a team composed of many developers working on two solutions (solution .sln in the Visual Studio sense). We use Visual Studio 2012. Most developers have access to only one solution but need binaries (and .h/.lib) from both.

We are moving toward the use of Team Foundation 2012 but previously used Visual SourceSafe 6.0.

We don't want to keep the binaries on the database (that would however allow developers to simply get them via a GLV. But life is not so simple...)

We need:

  1. Branches and binaries (from both solutions) in each branch. So if one develops in branch "1", he/she needs to use other solution binaries from branch "1".
  2. No binary pushed into database (since they can be rebuilt from code we don't want to increase the size of the database uselessly.)
  3. An easy way to obtain the up-to-date binaries (if not GLV, pre-build event?????? or something like this.)
  4. The possibility for the developers to keep the version of the binaries they have without getting the up-to-date version.

I strongly believe that there is a way to do what we need. After all we are surely not the only ones to have isolated teams that rely on other teams' binaries. I just don't know how to do it.

EDIT: GLV means "Get Latest Version". Sorry for the undefined acronym.

Upvotes: 1

Views: 209

Answers (2)

constructor
constructor

Reputation: 1410

Part of developers advise to use nuget.

Upvotes: 0

John Saunders
John Saunders

Reputation: 161783

Check the binaries into source control at various stages: releases, sprint ends, etc. Label the result of each version checked in.

The "other team" can take a branch from these binaries at particular label levels. They never need to know about the later labels until they're ready for them.

Upvotes: 4

Related Questions