We are going to create a new collection of Team Foundation Server for the next version of our application development. The source from our current version is largely inapplicable, with the exception of a few DLLs that should more or less remain unchanged. We wanted to create a new collection, but wondered if we could clone the DLL projects from our existing collection to save the story.
Is it possible? We understand that this can cause some “double maintenance” problems if there are any fixes for the DLLs, but we are not too concerned about this scenario.
So far I have come up with several resources. Some MSDN messages pointed out to people "Partitioning a collection of commands . " However, the problem is that you can only have one project in each collection. IT states:
A project cannot exist in more than one collection. Until you delete all duplicated projects between divided collections, you cannot run the renamed collection.
This is not what we want. We would like to support both projects with a history in each collection.
Otherwise, I saw the TFSConfig command. It contains the / clone option, but I'm not entirely sure about its use (additional examples are also hard to find), and it mentions that it is mainly used for separation.
Are we trying to do something that is impossible? Do we need to copy the source and add it as a new project to the new collection and reference the old collection if we really need a story? Thanks.
source share