1. Describe the bug
The AL Language extension enters a perpetual loading/spinning state when opening a multi-root .code-workspace that spans two repositories: a documentation-only repository (opened as ".") and an AL source repository (opened as a sibling path). The extension never completes initialization — IntelliSense, diagnostics, and CodeLens are unavailable.
2. To Reproduce
Steps to reproduce the behavior:
-
Check out both repositories side-by-side:
<customer>-docs/ ← documentation repo (MkDocs, no app.json)
<customer>/ ← AL source repo
-
Open the workspace file located in the documentation repo:
{
"folders": [
{ "path": "." },
{ "path": "../<customer>" }
],
"settings": {
"al.enableCodeAnalysis": true,
"al.codeAnalyzers": ["${CodeCop}", "${UICop}", "${PerTenantExtensionCop}"],
"al.ruleSetPath": "ruleset.json"
}
}
"." → Documentation repository — no app.json at root (MkDocs site, markdown only)
"../<customer>" → AL source repository — contains 3 AL projects nested under subfolders:
| Subfolder |
App ID |
platform / application |
AL files |
W1/<customer>.w1 |
2bb1a09a-… |
26.0.0.0 / 26.0.0.0 |
~31 |
BE/<customer>.be |
3fe87366-… |
26.0.0.0 / 26.0.0.0 |
~5 |
W1/<customer>.w1.Test |
8b7b806d-… |
depends on W1 + MS test libs |
~1 |
-
Observe the AL Language extension status bar item.
-
Wait — the spinner never stops and the extension never becomes ready.
3. Expected behavior
The AL Language extension completes loading for all 3 AL projects found in the "../<customer>" folder and provides IntelliSense, diagnostics, and CodeLens normally.
4. Actual behavior
The AL Language extension status bar item shows a perpetual loading/spinning indicator. [Attach screenshot or AL output channel log here.]
5. Versions:
- AL Language:
17.0.2273547
- Visual Studio Code:
1.127.0 (x64)
- Business Central Version:
28.1
- List of Visual Studio Code extensions installed:
ms-dynamics-smb.al@17.0.2273547
- Operating System:
Final Checklist
1. Describe the bug
The AL Language extension enters a perpetual loading/spinning state when opening a multi-root
.code-workspacethat spans two repositories: a documentation-only repository (opened as".") and an AL source repository (opened as a sibling path). The extension never completes initialization — IntelliSense, diagnostics, and CodeLens are unavailable.2. To Reproduce
Steps to reproduce the behavior:
Check out both repositories side-by-side:
Open the workspace file located in the documentation repo:
{ "folders": [ { "path": "." }, { "path": "../<customer>" } ], "settings": { "al.enableCodeAnalysis": true, "al.codeAnalyzers": ["${CodeCop}", "${UICop}", "${PerTenantExtensionCop}"], "al.ruleSetPath": "ruleset.json" } }"."→ Documentation repository — noapp.jsonat root (MkDocs site, markdown only)"../<customer>"→ AL source repository — contains 3 AL projects nested under subfolders:W1/<customer>.w12bb1a09a-…BE/<customer>.be3fe87366-…W1/<customer>.w1.Test8b7b806d-…Observe the AL Language extension status bar item.
Wait — the spinner never stops and the extension never becomes ready.
3. Expected behavior
The AL Language extension completes loading for all 3 AL projects found in the
"../<customer>"folder and provides IntelliSense, diagnostics, and CodeLens normally.4. Actual behavior
The AL Language extension status bar item shows a perpetual loading/spinning indicator. [Attach screenshot or AL output channel log here.]
5. Versions:
17.0.22735471.127.0(x64)28.1ms-dynamics-smb.al@17.0.2273547Final Checklist