Geek Answers Handbook

Best practices for sharing projects between decision trees (MSVS 2008 and MSVS 2010)

We have 50+ projects divided into 2 decision trees managed by TFS (version: Visual Studio 2008 / TFS RTM (9.0.21022.8)).

30+ projects are Visual Studio 2008 projects, and others are Visual Studio 2010

Newer projects use some old builds through binaries.

When developing new projects, we must make changes to the old builds, so we must simultaneously open 2 instances of MSVS.

Is there a way to share compiled sources with TFS between two different Studios decision trees? Or will we upgrade the decision tree 2008 to 2010? Does TFS 2008 support collaborative projects (or maybe they need to be updated as well)?

Thank you in advance!

+5
source share
1 answer

Andrew:

First, we break a couple of “best practices” to achieve this, but pragmatism is where the best practice matches the real world.

What we do is:

  • All binaries are checked in TFS in the LocalBin folder, which combines all our binaries.
  • All shared assemblies are located in the LocalBin / SharedBin folder.
  • The SharedBin folder forks into the top-level SharedBin folder in the consumer user project (s).
  • In a successful main build, LocalBin / Sharedbin merges with the SharedBin folders of the projects.

The result is something like this:

$/ProjectA/Main/Localbin/SharedBin $/ProjectB/Main/SharedBin $/ProjectB/Dev/Sharedbin ( $/ProjectC, $/ProjectD et cetera).

, MAIN-, MAIN, DEV, .

, , re loathe, ( ).

, , , , .

BTW, TFS2008 , , . - , , .

+6

More articles:


All Articles