Reuse launch configurations across workspace projects
Important
This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Dec 1, 2022 |
Dec 1, 2022 |
Business value
Visual Studio Code workspaces can save launch information so that it can be reused across projects in the workspace. This has, however, not been supported for AL, resulting in the need to copy launch.json configurations across projects. This isn't just an unnecessary nuisance, but also increases the risk of the configurations getting out of sync. With this release, you can now share a launch configuration.
Feature details
AL developers can now add a launch property to their code-workspace or to the settings.json file.
- A workspace launch configuration file overrides the launch configuration specified in the global settings.json file.
- A local launch.json file overrides the workspace and global configuration.
In cases where the local launch.json file doesn't contain a valid AL launch configuration, we'll try to find one in the code-workspace first, and then in the settings.json files. However, if the launch property is specified in the code-workspace file even without specifying a valid AL configuration, the global settings.json file will not be able to override it.
To learn more about how launch configuration in Visual Studio Code works, go to Debugging in Visual Studio Code.