Skip to main content

Using Github Copilot in Visual Studio

With GitHub Copilot you get autocomplete-style suggestions from an AI pair programmer as you code. Let me show you how to get started with Github Copilot in Visual Studio.

Remark: Before you can start you need to have an active GitHub Copilot subscription.

Install the extension

You can install the extension directly in Visual Studio.

  • Therefore go to Extensions –> Manage Extensions in Visual Studio.
  • Search for Github Copilot and click on Download.

  • After restarting Visual Studio, Visual Studio will ask you to active Github Copilot on your device. After walking through the device activation flow, you are finally ready to go.

Writing code with Github Copilot

Now that our extensions is up and running, let us write some code. When using Github Copilot it feels like you have a lot smarter Intellisense available.

I create a Book class and when I try to add a property Visual Studio is aware that I want to add typical properties for a book, so I get suggestions like title, author, etc…

I can hit Tab to accept the suggestion or Alt+; to get another suggestion:

If I want to see a whole list of possible suggestions, I can click on the Github Copilot icon at the bottom of my editor and click on Open Copilot. Now a separate Copilot window is loaded were I get a range of of possible solutions:

I can use one of the provided solutions by clicking on Accept solution.

Of course we can do more. A second thing we can do is writing a meaningful method signature and Github Copilot will try to understand what it should do and provide us with a suggestion.

For example I wrote an IsValidISBN() method to validate if the provided ISBN number is indeed a valid one. I could look up what are the validation rules for an ISBN number but Github Copilot already provides me a possible implementation:

A similar thing is possible through code comments. Use natural language to write a comment about what you expect. This can be one or more lines.

For example I asked Github copilot to write me an XUnit test for my IsValidISBN() method:

This is certainly a useful help to become a more productive developer.

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