Reputation: 33944
I have a TFS project that ought to be a folder under another project, so I want to move the source control history (We don't use the other features of TFS for this project, so I don't care about the project site). I've branched the code into the new location, and I'm preparing to delete the original project.
This SO question deals with the obviously lacking TFS feature of history after you branch, but since I'm deleting the trunk folder, this workaround functionality will break, and I'll completely lose my source history pre-branch.
Does anybody else have a better solution that would allow me to keep the history? I'd most like to retain the ability to do previous builds, and I lose that if I delete the trunk folder from source control, something which isn't acceptable. Thanks for your help!
Upvotes: 1
Views: 4144
Reputation: 20782
My recommendation is to use the Move (aka rename) feature. All history will be preserved in-place. And you can still recreate old builds in the other project by sync'ing back to the appropriate version.
If you do decide to Branch, it doesn't matter whether you delete the original source or not. Nothing in TFS is ever really deleted, simply placed into a "deleted state." History -- including merge history -- works identically. (Unless you also use the Destroy command. And even then, there's an option to delete the file contents & diffs but preserve the historical metadata.)
Upvotes: 1
Reputation: 755557
Another option to consider besides deleting the directory is simply cloaking it. Cloaking the directory won't actually remove anything from source code control. It will just prevent it from being checked out on your client. The end effect is it won't show up on your client and you'll still have the work around for history purposes.
Upvotes: 0