-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.NullReferenceException when clicking "Show at startup" on AL Home / Workspace file updated #7356
Comments
I unticked the option on the AL Home page, and put the following in to my user settings.json:
However, it has no effect: When I reopen VS Code, the tabs are not shown. Though my workspace file is unchanged (no al home/explorer property set): Edit: |
I'm getting a very similar error when the AL extensión starts to load a project:
VS Code: 1.78.2 (system setup) My workspace file is this:
|
Sorry. I've just discovered a syntax error in the
|
@NKarolak can you reproduce on the latest versions? We're unable to reproduce at this point. |
@SBalslev I can still reproduce it. Here's what I tested right now:
AL Output:
And Git indicates that the workspace file is still being updated with |
The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 23.0.11656.0 and VS Code Extension Version 12.0.842197. If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo For more details on code branches and docker images please read: |
Please include the following with each issue:
1. Describe the bug
Setting "Show at startup" on the AL Home page throws an error in the Output put.
2. To Reproduce
3. Expected behavior
No error in output. No update of the workspace file.
4. Actual behavior
Error in Output tab:
However, the workspace file has been updated:
But when I undo this change and reload VS Code, the change is back.
5. Versions:
The text was updated successfully, but these errors were encountered: