Skip to main content

TFS 2010: Go offline

TFS 2010 support offline clients. This means that you can continue to work although the TFS connection is not available. So if you start up VS and attempt to load a project contained in TFS and TFS cannot be found then VS will prompt you to work in offline mode.

TFSGoOffline

There is only one problem: VS only does this when loading a solution.  If TFS goes offline while a solution is already open though VS will not switch to offline mode.  Instead it'll keep trying to connect to TFS and then time out.  This is really inconvenient. 

So how can we tell TFS to go offline without having to reopen Visual Studio?

I’m aware of 2 options:

TFPT.exe
  • Open a Visual Studio 2010 command prompt
  • Run tfpt.exe with the ‘tweakUI’ option
  • Select the appropriate server and click Edit.
  • In the server properties dialog, check the Server is offline checkbox and click OK.
  • Now VS is in offline mode.  This takes effect immediately (even if VS is already open). 
Go offline extension
  • In Visual Studio go to File –> Source Control.
  • An extra Go Offline button should show up.

Remark: TFS 11 and VS 11 will support a far better model to work offline. 

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

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

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