Skip to main content

Visual Studio and Team Foundation Server : Fix bindings in solution file

For some time, I had an error when opening a specific Visual Studio solution. After a problematic merge operation, the Team Foundation Server Source Control binding information inside my solution file didn’t match with the projects I had in my solution.

If I opened up the sln file, I could find the following section:

Global
    GlobalSection(TeamFoundationVersionControl) = preSolution
        SccNumberOfProjects = 92
        SccEnterpriseProvider = {4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}
        SccTeamFoundationServer = http://mytfsserver:8080/tfs/defaultcollection
        SccLocalPath0 = .

The number of projects(92) was complete wrong. Visual Studio told me there should be 68 projects:

image 

I found an easy solution to fix this:

  • Close the solution in Visual Studio
  • Check out the .sln file. Open it with your favorite text editor.
  • Remove the GlobalSection(TeamFoundationVersionControl) section completely.
  • Close the .sln file and open the solution in Visual Studio.
  • The solution file is now no longer bound to Team Foundation Server so we should fix the binding.
  • Inside Visual Studio, go to File –> Source Control –> Advanced –> Change Source Control…
  • On the Change Source Control screen, select the .sln file and click on the Bind button

image

  • This will recreate the GlobalSection(TeamFoundationVersionControl) inside your solution file:

Global
    GlobalSection(TeamFoundationVersionControl) = preSolution
        SccNumberOfProjects = 68
        SccEnterpriseProvider = {4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}
        SccTeamFoundationServer = http://mytfsserver:8080/tfs/defaultcollection
        SccProjectUniqueName0

  • Check in the updated .sln.

Labels

Labels:

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...
Read more

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.
Read more

.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...
Read more