Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


TFS Best practice for team projects

TFS Best practice for team projects

TFS Best practice for team projects

Hi All,

I work in a small software house and have been asked to produce a migration path between VSS2005 and TFS2008 (using VS2008 Team Explorer).  I have managed to get most of the work done, but I have hit a bit of a roadblock concerning team projects.

Basically I have in the region of 200 top-level projects that I need to migrate.  Of these quite a lot can be moved into related groups, for example Project1 might have the following


What I am intending to do in TFS is the following:

$/Project1 (Team Project)
-----App1 (sub-folder)
-----App2 (sub-folder)
-----App3 (sub-folder)
-----App4 (sub-folder)

This would obviously reduce the need from 4 team projects to only 1.  However there seems to be a load of conflicting information on whether this is the best way to do it.  I'd appreciate it if any TFS experts could advise on the following:

1) Is this a good/practical way to do it?
2) If I do it this way can I ensure complete independence between the sub-projects - although they are linked in terms of a business solution we will never need to release them as a joint build, i.e. some files relate to console apps that are scheduled reguarly, some are winform apps etc.  I was intending to include the sln files in, for example $Project1/App1.
3) Will the revision history work ok using this method?




RE: TFS Best practice for team projects

By no means am I a TFS expert, but what you're describing sounds like a Project of Projects, which is available in TFS 2010, but sadly I don't believe it is in TFS 2008.

I'd be interested in hearing how you ended up configuring yours though...


"You guys pair up in groups of three, then line up in a circle."
- Bill Peterson, a Florida State football coach

RE: TFS Best practice for team projects



I've done further investigation and it would appear that the way I suggested initially is the only way I can do it in TFS2008. In TFS2010 there is the ability to have Team Project collections which allows you to have repositories that are completely separate, but it still wouldn't have matched what I needed.

As an additional requirement I have had to split further into Production and Development repositories, so I have ended up with a structure like this:


Repeat for Development

As I am only effectively creating 2 team projects it means I can't really use the documentation or bug tracking features. In 2010 I could have done the following:

<Production Team Collection>
$/<project1><application1> etc

<Development Team Collection>
$/<project1><application1> etc

This would have allowed me to create a team project for each distinct project, which would have been far better but I am having to use TFS2008 so not a lot I can do. On the plus side I have tested it and it seems to work....


RE: TFS Best practice for team projects

You still may be able to use the bug tracking work items along with Area Paths...


"You guys pair up in groups of three, then line up in a circle."
- Bill Peterson, a Florida State football coach

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close