Skip to main content

Github Copilot extension disabled after upgrading to Visual Studio 17.10.2

After upgrading my Visual Studio to 17.10.2, I got a warning that my Github Copilot and Github Copilot Chat extensions are incompatible with my Visual Studio version and will be disabled.

The following extensions are disabled because the installed version if not compatible with Visual Studio Pro 17.10.34505.107.
- GitHub Copilot
- GitHub Copilot Chat

I started to get a small panic because once you are used to have a Copilot assistant you never want to go back.

So after my Visual Studio was up and running, I opened the extension window and indeed both extensions were disabled:

I first tried to reinstall the extension but I got the same incompatibility message.

Does this mean that I can no longer use Copilot? Luckily the answer is no.  Starting from Visual Studio 17.10.2 Github Copilot and Copilot Chat are no longer separate extensions but became part of Visual Studio.

So although the extensions are no longer there, Copilot (Chat) was still available as I found out.

A better message would have helped to avoid the panic but the good news is I can continue my AI assisted code journey.

Happy coding!

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