Team Development with Visual Studio Team Foundation Server

The Tf move, delete, and rename commands are particularly useful if you need to
perform the operation on multiple files or folders. With Source Control Explorer, you can
only move, rename, or delete a single file or folder at a time.
Additional Resources
• For more information about the Tf delete command, see “Delete Command” on the
MSDN Web site at http://msdn2.microsoft.com/en-us/library/k45zb450(VS.80).aspx
• For more information about the Tf rename command, see “Rename Command” on
the MSDN Web site at http://msdn2.microsoft.com/enus/library/a79bz90w(VS.80).aspx
Only Delete and Rename with Your Solution Open
Delete and rename files inside Solution Explorer only with your solution open. Do not do
this directly on disk. This approach ensures that when you next check in your pending
changes, TFS source control is kept in synchronization.
Additional Resources
• For more information about the Tf delete command, see “Delete Command” on the
MSDN Web site at http://msdn2.microsoft.com/en-us/library/k45zb450(VS.80).aspx
• For more information about the Tf rename command, see “Rename Command” on
the MSDN Web site at http://msdn2.microsoft.com/enus/library/a79bz90w(VS.80).aspx
Create One Team Project per Application if You Want to Move Your
Assets Between Application Versions
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.