Skip to main content

Using GitHub Copilot with Visual Studio 2022

After requesting access to the GitHub Copilot a few days ago, I got good news today as my request was accepted. Time to give it a try in Visual Studio 2022.

Installing the GitHub Copilot extension for Visual Studio

GitHub Copilot in Visual Studio is possible thanks to the GitHub Copilot extension available on the Visual Studio Marketplace.

  • Open Visual Studio.

  • In Extensions | Manage Extensions, from the Visual Studio Marketplace, search for ‘Github Copilot’.  Remark: If you cannot find the extension, update your Visual Studio first.

  • Select the extension and click on Download to download and install the GitHub Copilot extension for Visual Studio.

  • Close Visual Studio to start the installation.
  • A VSIX launcher will start and you will be asked to confirm the installation. Click on Modify to continue with the installation process.

Use GitHub Copilot for the first time

After the installation has completed, we need to activate the extension.

  • Open Visual Studio again.
  • Create a new project to test GitHub Copilot. Multiple languages are supported by I gonna try C#.
  • You are welcomed by a popup that asks you to enter a device code on the Github device authorization page

  • A device activation code is copied to the clipboard and a browser window is opened where you can paste the activation code.

  • As a last step we need to read and approve the Telemetry terms. Click Yes to continue.

  • Start typing a function header. For example, I typed

bool IsLeapYear(

  • CoPilot does it’s magic and offers me the following suggestion(in grey);

  • Hit Tab to accept the suggestion. If you don’t like the provided suggestion, you can see alternate suggestions by pressing Alt+. (or Alt+;).
    Labels:

    Popular posts from this blog

    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

    Cache stampede: when our cache turned against us

    While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
    Read more

    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