This project is read-only.

How to Manage Shared Binaries

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

Managing shared binaries is similar to managing shared source: you must decide where you want to store the binaries and how you want your team to access the binaries.

The following options are available for storing the binaries:
  • If the shared binaries are clearly owned by a particular team, store the binaries in their team project.
  • If the shared binaries have no clear ownership, create a team project specifically for the shared binaries.

The following options are available for using the binaries in another project:
  • Shared binaries are usually updated only periodically. If this is the case, branch from the shared location into the consuming team project. When the binaries change, you can execute a merge to get the latest version.
  • If you need to stay synchronized with the shared binaries at all times, map the source from the shared location into a local workspace on the client machines.

To branch shared binaries into your project
  1. In Source Control Explorer, right-click the root folder of Shared Binaries.
  2. Select the Branch option.
  3. In the Branch dialog box, set the Target to the root folder of the Client team project, and then click OK.
  4. After the branch operation has completed, do not forget to check in the branched source code.

Whether you use workspace mapping or branching, you should se naming conventions that make it clear where the shared binary location is in your project; for example:
  • Main
    • Source – Contains code for this project
    • Lib – Contains shared binaries

Additional Resources

Last edited Jul 31, 2007 at 3:33 PM by prashantbansode, version 6


No comments yet.