Skip to main content

Both Visual Studio and Team Foundation Server get GIT support

Last week at the ALM Summit Brian Harry did some exciting announcements: .

  1. Team Foundation Server will host Git repositories – and more concretely, Team Foundation Service has support for hosting Git repositories starting today.
  2. Visual Studio will have Git support – and concretely, Microsoft released a CTP of a VSIX plugin for the Visual Studio 2012 Update 2 CTP today.
Resources
  • You can get a good overview of how to get started (including all the download links) by reading this tutorial.
  • Watch this video for a 10 minute walk-through.
  • Also you can read the news and the Learn content on the Team Foundation Service welcome portal.
  • And don’t forget to have a look at Scott Hanselman’s opinion about it.

    I think this is really great news, Microsoft not only decides to support Distributed Version Control Systems(DVCS) but also  choose to integrate with the most popular DVCS Git(and all available services built on top of it).

    Most important question of course is when will this ship?

    “This” has many piece so let’s talk about each one in turn:

    • Team Foundation Service – As of today you can host Git repos in TFService projects. It is “shipping” now and ready for use.
    • Team Foundation Server – The plan is to include Git support in the next major release of TFS. No date has yet been announced.
    • Visual Studio 2012 support – A VSIX is provided today. It is a “community technology preview” of the Git VSIX on top of a “community technology preview” of VS 2012 Update 2 (VS2012.2).
    • Visual Studio V.Next – The Git plugin will be integrated into all editions of Visual Studio V.Next (including Express) and will appear in the various pre-releases and RTM.

    vs_heart_git

    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