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.

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

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.

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should