Skip to main content

TFS 11 Power Tools beta

Microsoft shipped a beta version of the Team Foundation Server Power Tools that work with VS 11 and are optimized to work with TFS 11.

This Power Tools release is designed to work with a VS 11 client (or Team Explorer 11) but you won’t get the VS integration in a VS 2010 or earlier client.

This beta gives you the most useful Power Tools up and running with VS 11/TFS 11. Some of the features of the previous Power Tools are removed because they have  been integrated into the product and At the moment no new features are added instead.

The features included in this release are:

  1. TFS Power Tools
    1. TFPT Command Line
    2. The Team Explorer extensions – All are included except work item templates.
    3. Windows Shell Extension – It’s been enhanced to support local workspaces meaning no more read-only files and need to checkout, better offline support and everything else that comes with local workspaces.
    4. Process Template Editor – We’ve added support for all of the new process features in TFS 11, however some of the implementation is place holder – for instance, editing the agile project management configuration involves editing XML.
    5. Best Practices Analyzer
    6. Test Attachment Cleaner
    7. TFS Powershell commands
  2. Build Extensions
  3. MSSCCI (32-bit) & MSSCCI (64-Bit)
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