version control - TFS: Hundreds of separate applications/projects - what's the best approach? -

Suppose that the company has a large number of small medium applications, which can be logically divided into smaller groups.

.

For example, I can apply for BMW, Mazda, Honda, Ford .... Kawasaki, Harley, ... a few dozen or even hundreds of applications.

> I think I have 2 options in TFS:

1. Create a separate project for each application. I end up with a lot of small projects and may be affected by the boundary, but the advantage is that I have all the projects, bugs, reports etc., which each project is put separately and a portal for each project is.

2. Create a project 'car' and a project 'motorcycle', and under each project create a source control tree with each branch for each app. It will provide a better structure and less overhead, but I can not have a portal and list of different operators, bugs, reports etc. for 'Honda' and for different 'BMW'.

Am I missing something? A separate list of methodology to create a stack of projects with the risk of killing the TFS limit on the number of projects, both of the insects have a method for each small project?

I will go with 2 points. You can use the 'Regions' section of TFS to assign work items to a particular sub-project.

For those small apps, there is a lot of overhead in creating whole team projects. Do each of these apps need a completely independent life cycle, a collaboration tool (WSS site) and a set of reports? Usually not

The worst case is that you can create a new team project for any of them if it becomes too big for management, because when you make projects and go to the source control screen Since then, 'There is an option from the branch existing project' so that you can maintain your source history and make a dedicated project.

Scroll tightly as a starting point.