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:

Popular posts from this blog

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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more