Skip to content

[Bug] AL Language Extension initializes forever if used with an external ruleset file #8327

Description

1. Describe the bug
AL Language Extension initializes forever if used with an external ruleset file.

2. To Reproduce
Steps to reproduce the behavior:

  • Use a workspace file. I have not tested if the issue occurs without a workspace.
  • Set "al.ruleSetPath": "../.vscode/any.ruleset.json",
  • Add a file to that path, referencing a ruleset file containing an url:
    "includedRuleSets": [
        {
            "path": "https://any.valid.url/al-rulesets/any.ruleset.json",
            "action": "Default"
        }
    ],

3. Expected behavior
Normal workspace loading.

4. Actual behavior
The workspace loads forever...

Loading workspace:  : Preparing project: 'AAR-app'

5. Versions:

  • AL Language: 18.0.2668733
  • Visual Studio Code: 1.134.0
  • Operating System:
    • Windows
    • Linux
    • MacOS

Internal work item: AB#648176

Activity

  1. MODUSCarstenScholling commented on Aug 28, 2026

    @MODUSCarstenScholling
    Author

    The conclusion of the AI triage is wrong. A little common sense would have made that clear.

    Name: AL Language extension for Microsoft Dynamics 365 Business Central
    Id: ms-dynamics-smb.al
    Description: Development tools for Dynamics 365 Business Central
    Version: 18.0.2668733
    Publisher: Microsoft
    VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al
    

    It doesn't matter whether there is a workspace file or not. Both opening .code-workspace and opening “app” as a folder (with the corresponding settings.json) result in this issue.

    .vscode/settings.json:

    {
    	"al.ruleSetPath": "./.vscode/any.ruleset.json"
    }

    .vscode/any.ruleset.json:

    {
        "name": "Any Ruleset",
        "includedRuleSets": [
            {
                "path": "https://any.al.ruleset.com/test.ruleset.json",
                "action": "Default"
            }
        ],
        "rules": [
        ]
    }

    Look at the image. Started at 08:56 and still working at 09:09...

    Image
  2. Ugniusig commented on Sep 2, 2026

    @Ugniusig

    have the same issue, changing to pre-release worked, but then publishing becomes the problem.

  3. someC0d3r commented on Sep 3, 2026

    @someC0d3r

    Also the same issue, but happens with the pre-release version when loading an AL project it initializes forever... Removing the external ruleset worked for me for the moment.. :(

    Edit:
    AL Language Extension version: 18.0.2668733
    AL app: 29.0.0.0 (application+platform), runtime: 18.0

  4. zeande commented on Sep 9, 2026

    @zeande

    Any chance this would could get some traction? With the 18.0 version just moving to release, our whole team is affected. For us, it also had to do with loading the external rulesets from our app.ruleset.json file.

    cc: Steffen Balslev (@SBalslev)

  5. SvenPouwels commented on Sep 9, 2026

    @SvenPouwels

    We're encountering the exact same issue. Disabling the external ruleset in the user settings of VSC works, but is not a workaround since we need our external ruleset for our company code standards to be properly applied.

  6. thpeder commented on Sep 9, 2026

    @thpeder
    Member

    I'm working on the fix for this, and is aiming at getting a new version out tomorrow.

  7. MODUSCarstenScholling commented on Sep 10, 2026

    @MODUSCarstenScholling
    Author

    Was it really necessary to rush out a “final” version without testing it and thereby multiply the number of people experiencing bugs?? Especially this known bug? Oh boy...

  8. PeterConijn commented on Sep 10, 2026

    @PeterConijn

    We are encountering this as well. Thanks for narrowing down the cause to external rulesets.
    We'll be anxiously awaiting the fix.

  9. NKarolak commented on Sep 10, 2026

    @NKarolak
    Contributor

    Thomas Pedersen (@thpeder) I can confirm that v18.0.2732683 solves the issue, thank you!

  10. PeterConijn commented on Sep 10, 2026

    @PeterConijn

    Thomas Pedersen (@thpeder) Confirmed here too. v18.0.2732683 resolves the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions