Skip to main content

Team Foundation Server: How to migrate TFS Version Control project by project–Part 2

If you want to migrate a full TFS collection, support is built-in. But what if you want to migrate a specific project but want to keep the source code history?

I blogged about a solution I used before by using Git as a way to move code between 2 TFS Version Control repositories. (Here is the link in case you cannot find it: http://bartwullems.blogspot.be/2015/05/team-foundation-server-how-to-migrate.html). I used this approach multiple teams with great success.

However some people who tried to do the same thing complained that the approach I described didn’t work when you have multiple branches. So time to solve this and add the misssing steps required to migratie multiple branches:

[core]

repositoryformatversion = 0

filemode = false

bare = false

logallrefupdates = true

symlinks = false

ignorecase = true

hideDotFiles = dotGitOnly

autocrlf = false

[git-tfs]

ignore-branches = False

[tfs]

touch = 1

[tfs-remote "default"]

url = http://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Main

[tfs-remote "Development/Feature1"]

url = http://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Development/Feature1

[tfs-remote "Development/Feature2"]

url = https://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Development/Feature2

[tfs-remote "Releases/Release1"]

url = http://oldtfs:8080/tfs/DefaultCollection

repository = $/BranchingDemo/Releases/Release 1

[tfs-remote "BranchingDemo"]

url = http://newtfs:8080/tfs/DefaultCollection

repository = $/NewRepository/DevFeature1

  • Initialize the remote
    • git-tfs branch –i BranchingDemo
    • This disconnects the branch from the current remote and connect it to the new TFS server
  • Switch between all branches and execute the following commands:
    • ​git checkout "branchname"
    • git tfs branch $/TargetProject/TargetBranch --comment="branch X" 

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...