tfs - source control

[Goksly]

Does anyone have any experience with team foundation servers source control... Just want to know the best way to store our source control. We have a number of web applications that share the same business logic and data access... But when people are checking things out and building etc, it should just do the three or four projects which the application needs.
Cheers.

 

[ZombieFan]

We use TFS in work. Our source control is structured so the tree looks something like this:

|
|- Projects
 |- Company.Proj1
  |- Company.Proj1.csproj
  |-     <source code>
  |
 |- Company.Proj2
  |- Company.Proj2.csproj
  |-     <source code>
  |
 |- Company.Proj3
  |- Company.Proj3.csproj
  |-     <source code>
|
|-Solutions
 |- Application1
  |- Applicaiton1.sln
  |
 |- Application2
  |- Applicaiton2.sln
|

So each project has it's own seperate folder under the 'Projects' folder as you would expect. We also have a seperate 'Solutions' folder in which we store a .sln file for each seperate applicaiton we build. Each .sln file contains the projects which that application requires. So 'Applicaiton1.sln' may have 'Company.Proj1' and 'Company.Proj3' included in it. Application2.sln may have 'Company.Proj2' and Company'Proj3' in it.

Does that make sense? The key thing is that the 'Solutions' section only contains .sln files and no project source code. When developing, developers should only work by building the projects by loading the correct .sln file.

We also have build automation set up. Whenever a check-in occurs, all the solution files stored in TFS are built automatically

 

[Goksly]

Hmmm interesting way to do it! Will give that a go. Thanks.