TFS 2010 - how should I convert VS shared library solutions to "team projects"?
I am new to TFS (and branch / merge style source management). I read in the 2010 TFS Branching Guide, but I'm getting a bit out of the way of how my solutions are supposed to map to the original control. I think my main problem is how to figure out the best placement of class libraries to be shared between solutions.
Our environment is a business-to-business environment with about a dozen separate web applications and about half a dozen class libraries shared between web applications. Our solutions usually consist of one of a web application, a unit test project, library class support projects, and any third party assembly references.
Thus, two representative solutions are as follows:
SOLUTION A
- WebApp11 Project - WebApp11UnitTests Project - ClassLib11 Project
- ClassLib22
Project
- ClassLib33
Project
- bin \ *. dll
SOLUTION B
- WebApp22
Project
- WebApp22UnitTests
Project
- ClassLib11
Project - ClassLib22 Project - ClassLib44 Project - ClassLib55 Project
- bin \ *. dll
How should they be structured in TFS?
Do we create a team project for each solution, so that ClassLib11, for example, will belong to both TEAM SOLUTION A and TEAM SOLUTION B?
I think so, so each team project consists of everything that is needed to deploy.
What if we use a couple of different solution files, for example, one large solution file that has every web application and every class library? Where does this solution fit?
a source to share
We store all of our production applications (we have a set of applications with significant overlap) in a single TFS project. This allows them all to manage the same rules as they are probably all changed by different people all the time, but one person sometimes / often has scenarios that they are interested in in many different applications together.
a source to share