The file .vscode/extensions.json allows you to recommend extensions when opening a workspace or project in VS Code. This way, each developer who opens the repo will see a prompt to install (with one click) the recommended extensions and work with a consistent environment.
What is the extensions.json file in VS Code?
- It is a JSON file located in the .vscode/ folder of your project.
- Its main purpose is to recommend extensions (it does not install them forcibly) identified by their ID (publisher.extensionName).
- VS Code shows a notification when opening the workspace with the option to install all or review the list.
Importance of extensions.json in AL and Business Central projects
In AL teams, having everyone use the same extensions prevents discrepancies in formatting, static analysis, naming conventions, and speeds up common tasks.
- AL language and official snippets.
- Refactoring and AL utilities.
- Additional linters and CodeCops.
- Automated testing.
- Translations/XLIFF, object IDs, GUIDs.
- Docker / Dev Containers.
- Git / GitLens, REST Client, etc.
Minimum structure of the extensions.json file
File: .vscode/extensions.json
{
«recommendations»: [
«ms-dynamics-smb.al»,
«andrzejzwierzchowski.al-code-outline»,
«waldo.crs-al-language-extension»,
«rasmus.al-formatter»,
«jamespearson.al-test-runner»,
«waldo.nab-al-tools»,
«vjeko.vjeko-al-objid»,
«ms-azuretools.vscode-docker»,
«eamodio.gitlens»,
«humao.rest-client»
]
}
How to create and maintain extensions.json in your repository
- Create the .vscode/ folder at the root of the repo.
- Add the extensions.json file with the “recommendations” section.
- Confirm the correct IDs in the VS Code Marketplace.
- Commit the changes to version control.
- Ask the team to open the repo in VS Code and accept the recommended installation.
Relationship of extensions.json with other JSON files in AL
- app.json → manifest of your extension.
- launch.json → defines how your extension is published and debugged.
- extensions.json → does not affect compilation or deployment, it only improves the development experience.
Practical example of using extensions.json
Good practices when using extensions.json
- Document in the README.md why you recommend each extension.
- Version the file and review it in PRs.
- Avoid duplicates with extension packs.
- Coordinate its use with the workspace settings.json.
Frequently asked questions about extensions.json
Do the extensions in extensions.json install themselves?
No. VS Code only recommends them and the user must confirm.
Does it affect the compilation or publishing of my AL extension?
No, not at all.
Where can I verify the correct extension IDs?
In the Visual Studio Code Marketplace.
ABD and professional development in Business Central
En ABD Consulting and IT Solutions we work daily with Business Central and AL development teams, helping them standardize environments, improve code quality, and accelerate development cycles.
From the definition of homogeneous workspaces in VS Code to the implementation of DevOps best practices, CodeCops, and automation, we support technical teams so they can focus on what matters: developing robust and scalable solutions for Business Central.
Do you want to improve your AL team's productivity and quality? Contact ABD and we will help you optimize your development environment.