Skip to main content

Getting started with GitHub Copilot in VS Code

GitHub Copilot is an AI peer programming tool that helps you write code faster and smarter. It can suggest code completions,, generate code snippets, and even write entire functions for you. GitHub Copilot works with a variety of languages and frameworks, and it can learn from your own code and preferences. By installing GitHub Copilot in VS Code or Visual Studio, you can leverage the power of AI to enhance your coding experience and productivity.

Prerequisites

Before you can install GitHub Copilot in Visual Studio, you need to have the following:

  • A GitHub account. (sign up for free at github.com)
  • An active GitHub Copilot subscription (Individual, Business, or Enterprise).
  • VS Code installed or Visual Studio 2022 17.6 or later installed.
Installation
To install GitHub Copilot, open VS Code and go to the Extensions tab. Search for GitHub Copilot.

When you install Copilot in Visual Studio Code, you get two extensions:
  • GitHub Copilot - Provides inline coding suggestions as you type.
  • GitHub Copilot Chat - A companion extension that provides conversational AI assistance.
Select the  GitHub Copilot extension and click Install

Select the GitHub Copilot Chat extension and click Install. (Restart VS Code if reequired)

Click on the "Toggle chat' button to open GitHub chat, or quick chat window.
If you have not linked your GitHub account in VS Code previously, you will prompted to authenticate with your GitHub Account.

That's it! Now you can start using GitHub Copilot.

Additional resources

Labels:

Comments

Post a Comment

Popular posts from this blog

User Security Governance (Preview) feature in D365 FO

Let's take a first look at User security governance . It is the latest set of features in the D365F&O 10.0.43 update which provides useful tools to System administrators for role management, licenses auditing, enhanced audit trails and versioning, supported with some useful very useful reports around license usage, separation of duties violations etc. Key aspects of this feature include: Role Management: Improved tools for creating, modifying, and managing user roles. Audit Trails: Enhanced tracking of changes made to security settings, helping administrators monitor and review security configurations. Compliance: Tools to ensure that security settings comply with organizational policies and regulatory requirements. Feature management A new feature called (Preview) User security governance has been added to Feature management to control the overall functionality. Navigate to System administration > Security > Security governance to explore all the features. Security analy...
Post a Comment
Read more

Microsoft Dynamics 365 FSCM Licensing - New Multi-License Mapping on Menu Items

Licensing in enterprise systems has long been a game of mapping menu items to license types, ticking boxes, and hoping your role design didn’t trigger unexpected costs. But with the 2025 updates to Dynamics 365 Finance and Operations, Microsoft has flipped the script—ushering in a smarter, more flexible model that reflects how users actually work. Let’s break it down. In the legacy model, each menu item was tied to a single license type. For instance, if a user accessed MenuItemA that had a Finance license type on it, they needed a Finance license. If they accessed MenuItemB with SCM assigned on it, they needed SCM. Simple? Yes. But also rigid, prone to over-licensing, and blind to real-world role overlap. Example:  This model treated licensing like a static blueprint—ignoring the nuance of blended roles, attach licenses, and shared responsibilities across departments. Fast forward to 2025. Microsoft’s new licensing logic is object-level, dynamic, and context-aware. Now, a single m...
2 comments
Read more

Conditionally Hiding Menu Items in D365 FinOps Menus Without Using Feature Keys

In Microsoft Dynamics 365 Finance and Operations (D365 F&O), menu items are the links that can be clicked on to access forms, reports, classes, jobs, and queries. Feature keys are typically used to control the visibility of menu items based on user licenses. However, there are scenarios where you might want to hide menu items conditionally without relying on feature keys.  This can be accomplished by extending the 'SysMenuNavigationObjectFactory' class and modifying the checkAddSubMenu(...) method.  Suppose we want to hide the  Vendor payment journal menu item under Accounts payable > Payments > Vendor payment journal Steps 1. Create an extension of the SysMenuNavigationObjectFactory class [ ExtensionOf ( classStr (SysMenuNavigationObjectFactory))] internal final class SysMenuNavigationObjectFactory_PS_Extension { } 2. Create a Chain of Command (CoC) for the checkAddSubMenu method [ ExtensionOf ( classStr (SysMenuNavigationObjectFactory))] internal final...
Post a Comment
Read more