Dynamics 365 Business Central: Support for global and workspace launch configuration (No launch.json file is required)

Dynamics 365 Business Central

Hi, Readers.
Minor update 21.1 for Business Central 2022 release wave 2 has been released last week. Learn more: Link.
Today I would like to share a new feature “Support for global and workspace launch configuration” from BC 21.1.

PS: This information is not mentioned in What’s new and planned for update 21.1, but is recorded in AL Language Changelog version 10.1 (AL Release Notes).

Support for global and workspace launch configuration

AL developers are now able to add a launch property to their code-workspace or settings.json file and it will be taken into account. A local launch.json file overrides the workspace and global configuration. A workspace launch configuration overrides the launch configuration specified in the global settings.json file.

In case that 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.


Let’s see more details.

Now you can find Launch setup in VS Code Settings.

Global debug launch configuration. Should be used as an alternative to ‘launch.json’ that is shared across workspaces.

User settings:

Workspace settings:

Choose Edit in settings.json to open settings.json file.

Yes, now, we can add the launch configuration to settings.json, no need to repeat the settings every project.👏🎉


Test Video:

Give it a try!!!😁


Hope this will help.

Thanks for reading.



Copied title and URL