AL-Go requires app.json in project subfolder, but VS Code AL extension needs it in workspace root - how to resolve conflict? #1908
-
I'm experiencing a conflict between AL-Go workflows and VS Code AL extension requirements regarding
My Problem1. VS Code AL extension works when
2. AL-Go workflows fail when
3. When I move
What I've tried
Is there a standard solution for this common scenario where developers want to use both AL-Go automation and local VS Code development? Am I doing it wrong, please help me undertand how the environment should be configured. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
For point number 3; It should be possible to make the VS Code Extension work when the code is under the src folder. I see you already have a workspace file. What is it that doesn't work if you open up the workspace ( Here are the docs on |
Beta Was this translation helpful? Give feedback.
For point number 3; It should be possible to make the VS Code Extension work when the code is under the src folder.
I see you already have a workspace file. What is it that doesn't work if you open up the workspace (
./code repository-root/al.code-workspace
) with the code under the src folder? That should be supported as far as I know.Here are the docs on
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-multiroot-workspaces
https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-work-workspace-projects-references