TFS2010: move source with history and then delete old project without losing history?

Question

Context: I currently work as an intern at a company that switched to TFS 2010 from VSS. TFS has been used here for a couple of months, but in the early period after that some "mistakes" were made when creating projects. After that, the need for a custom team project template was recognized. The template was developed and is being implemented in the organization. (small website development company, many small projects)

Question: We are trying to transfer old projects to a new template by setting up new objects using a custom template. We would like to transfer the sources of old projects to projects using the new template. Source history should be maintained for reasons of support. It is not advisable that old projects appear in the Team Collections Team list of teams, so we would like to hide them if deletion is not an option. (to reduce the amount of garbage in the list)

I have some solutions in my opinion to do this work, but I'm not sure that they will work. (even spending some time researching the problem online)

1: Running a branch from the old project to the new one, and then deleting the old project. I think he should preserve the history of the old project. Some people here very loudly declare that this is not so, which causes some struggle. Before clicking this option, I would like to make sure that it works.

2: Take a migration tool to transfer sources between projects (possibly through a temporary collection of commands). I read that this may be an option, but the details of how to carry out such a move are still not clear. This seems to have a lot of caveats associated with it and can be cumbersome to enforce. (I'm not a superman when it comes to these issues, but nobody else is here) The Migration Guide seems to suggest that this is possible, but I cannot determine if this scenario is supported, and how to recover if something goes well not this way.

Perhaps you can create new projects and hide old projects from the list of team collections of collections without deleting them? (I wonder if there is some kind of inactive setting for team projects, I can’t find such an option after studying the tfsconfig tool in the admin console).

An explanation of how best to satisfy this problem and possible solutions would be much more receptive.

Answer 1

Running a branch from an old project to a new one, and then deleting the old project. I think he should have the story of the old project deleted.

I am sure that if the project of the old team is deleted, the part of the history associated with this project of the team will also disappear, see here for more details. You can confirm this by running a quick test if you want.

Perhaps it is possible to set up new projects and hide old projects from the team of team collectors list of projects without deleting them?

Basically, you can achieve this by denying read access (GenericRead) to most users in older team projects. Of course, for administrators of a collection of projects that by default have this permission in all team projects, projects of old teams are still displayed in the list for them.

Good luck

Answer 2

There is no solid relationship between a team project and a specific part of the version control tree. Say you have a team project called Error. You have a source in "$ / Mistake". Now you can create a new team project called "Got It Right" and specify whether to use the sources in "$ / Mistake".

Answer 3

Use the source explorer to move the solution between projects. Here's what projects and solutions look like before moving a solution.

Move selection found either with

• right-click on the solution by selecting "Move" from the drop-down menu
• Select a move from the Source Control menu found in the File section of the drop-down menu