Create One Team Project per Application if You Want to Move Your Assets Between Application Versions

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

If you want to carry forward not only source code but also work items and other TFS assets between releases, consider using one team project per application. When you use a single team project for multiple versions of the application, all of the TFS assets are carried forward automatically for you for the next release. When you are ready to release a new version of your application, you can create a branch within the project to represent the release and isolate that code.

If you choose to use one project per application, keep the following vulnerabilities in mind:
  • Releases in parallel are forced to share work item schemas, check in policies, and process guidance.
  • Reporting is more difficult. Because reports default to the entire project, you must add filtering by release.
  • If you have hundreds of applications, each in its own project, you will run up against TFS performance and scale limits.
  • You will accumulate ‘baggage’ over multiple releases. The easiest way to address this issue is to create a new project and then branch code you want to carry forward into that project.

Additional Resources

Last edited Jul 26, 2007 at 11:34 AM by prashantbansode, version 3

Comments

No comments yet.