AL Language extension 8.4

Changelog on the Visual Studio Marketplace · Business Central 2021 release wave 2

Validation of runtime breaking changes

In order to call AL procedures, the Business Central runtime relies on a unique ID assigned to each procedure. When a procedure changes its signature, its method ID changes too and dependent extensions which are referencing it must be recompiled in order to use the new ID. Some signature changes do not have an impact on the compilation of dependent extensions, but are still causing the generation of a new method ID. For example, adding a var parameter, or adding a return type. These changes are called runtime breaking changes.

In order to prevent runtime issues caused by runtime breaking changes and provide a better experience to customers in SaaS, a new AppSourceCop rule AS0102 has been introduced and the severity of the rules AS0077 and AS0078 has changed from Warning to Error.

These changes have already been applied to the technical validation of AppSource submissions in Partner Center.

GitHub Issues

• #6892 Implementing Interface with Complex Return Type Creates Incorrect Signature
• #6927 Cannot remove obsolete controladdin
• #6872 Can’t Go To Definition of fields used in key
• #6851 AL0697 - Valid Fieldtype Fielref.Value() –> New Cast AsGuid, As DateTime

Warnings that will turn into errors in the next releases

Over the last periods, we have introduced multiple warning diagnostics that will turn into an error in a future release. You can find a summary below:

• Warning AL0660 will become an error with Business Central 2022 release wave 2.
• Warning AL0677 will become an error with Business Central 2022 release wave 2.
• Warning AL0692 will become an error with Business Central 2022 release wave 2.
• Warning AL0694 will become an error with Business Central 2022 release wave 1.
• Warning AL0697 will become an error with Business Central 2022 release wave 2
• Warning AL0711 will become an error with Business Central 2023 release wave 1.
• Warning AL0715 will become an error with Business Central 2022 release wave 2.

Miscellaneous

The way projects are loading in a workspace has changed. While the active project and its project references are loaded no compilation-based information like IntelliSense, symbols are available. Depending on the number of files in the project reference closure of the active project, this operation can be time-consuming. Projects in a workspace that are not loaded are marked with letter N. A project will load if it is made active by opening an AL file, or the app.json.

Source: Visual Studio Marketplace, ms-dynamics-smb.al changelog, Microsoft’s text unchanged. Dates from the gallery’s upload records.