AI-Part2: Setup-Vscode-al-copilot-business-central
Setting up Visual Studio Code, the AL Language extension, and GitHub Copilot for Business Central AL development requires installation of three components and verification of connections. This post guides developers through each setup step and highlights common gotchas like extension version mismatches and separate subscription management.
Read it hereOpen in Claudetag-blogger-com-1999-blog-3122193036149030463-post-4656464818096012006--003bfcdd4e.md
post Saurav Dhyani
"Microsoft recommends pulling the AL Language extension version that ships directly from that container, rather than the Marketplace version, to avoid compiler-version mismatches"
Key points
- Install VS Code as the only Microsoft-supported IDE for AL development, then add the AL Language extension from either the Marketplace or your BC container version
- Run the AL: Go! command to create project structure, connect to your BC tenant, and download necessary symbols for standard BC objects
- GitHub Copilot requires a separate subscription from both BC licenses and VS Code, so verify the subscription is active during extension installation
- Test the full setup by publishing the sample AL file to your sandbox and running /explain commands in Copilot Chat to confirm all components communicate
- Disable telemetry in VS Code settings if data privacy is a concern
Quotes
- “Microsoft recommends pulling the AL Language extension version that ships directly from that container, rather than the Marketplace version, to avoid compiler-version mismatches” (Provides critical guidance on selecting the correct extension version to prevent compilation errors in specific BC environments)
Context
- Features: AL Language extension, GitHub Copilot, Copilot Chat, AL: Go! command, Symbol download, Project scaffolding
Source: Saurav Dhyani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.