Please include the following with each issue:
1. Describe the bug
Debugging AL on the VS Code opened in the host machine of a remote tunnel cannot display the content of the file in which the breakpoint or error occurs.
2. To Reproduce
Steps to reproduce the behavior:
I am using remote tunnel.
(1) Set up remote tunnel using VS Code on Windows host with either GitHub or Microsoft account. --> This is the host
(2) Connect to the remote tunnel using VS Code (on Windows or Linux). --> This is the guest
(3) In the guest's VS Code, open an AL project folder/workspace.
(3) In the guest's VS Code, everything works great; I can code and publish with AL extension as per normal.
(4) In the guest's VS Code, publish or download symbols for the first time to trigger request for developer authentication in the web browser.
(5) In the guest's VS Code, attach a debugger from a running BC SaaS session and perform some operation in BC that causes error to trigger debugging breakpoint in VS Code.
AL code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally.
No codes; this is generic debugging issue, not coding issue.
Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
3. Expected behavior
A clear and concise description of what you expected to happen.
Related to step (4):
When publishing/downloading symbols for the first time, I'd expect the authentication shall open in the guest machine with the remote host machine's credentials. Because if not, if the host is a standalone server, that would mean every developer that remotely connect to the host will have to RDP into the server to authenticate themselves, which makes no sense.
Related to Step (5):
The .AL file content in which the debugging breakpoint or error occurs should be able to display the content of the remote file in the host machine as if the file is a local file and the debugger can function fully as if it is debugging a local AL object file.
4. Actual behavior
A clear and concise description of what happened accompanied by images, animations, or a link to a video showing the issue occurring
Related to Step (4):
When publishing/downloading symbols for the first time, the request for developer authentication is opened in the remote host machine, instead of the guest machine.
Related to step (5):
When I attach a debugger from a running BC Online session in the remote guest machine though, debugging can be attached, breakpoint can be captured, however, the .AL file in which the breakpoint occurs cannot be displayed. A one-line error stating "No content available." appears.
5. Versions:
- AL Language: 17.0.2273547
- Visual Studio Code: 1.134.0
- Business Central: 28.0.53614.0
- List of Visual Studio Code extensions that you have installed:
AL Language extension for Microsoft Dynamics 365 Business Central
- Operating System:
Final Checklist
Please remember to do the following:
Please include the following with each issue:
1. Describe the bug
Debugging AL on the VS Code opened in the host machine of a remote tunnel cannot display the content of the file in which the breakpoint or error occurs.
2. To Reproduce
Steps to reproduce the behavior:
I am using remote tunnel.
(1) Set up remote tunnel using VS Code on Windows host with either GitHub or Microsoft account. --> This is the host
(2) Connect to the remote tunnel using VS Code (on Windows or Linux). --> This is the guest
(3) In the guest's VS Code, open an AL project folder/workspace.
(3) In the guest's VS Code, everything works great; I can code and publish with AL extension as per normal.
(4) In the guest's VS Code, publish or download symbols for the first time to trigger request for developer authentication in the web browser.
(5) In the guest's VS Code, attach a debugger from a running BC SaaS session and perform some operation in BC that causes error to trigger debugging breakpoint in VS Code.
No codes; this is generic debugging issue, not coding issue.
Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
3. Expected behavior
A clear and concise description of what you expected to happen.
Related to step (4):
When publishing/downloading symbols for the first time, I'd expect the authentication shall open in the guest machine with the remote host machine's credentials. Because if not, if the host is a standalone server, that would mean every developer that remotely connect to the host will have to RDP into the server to authenticate themselves, which makes no sense.
Related to Step (5):
The .AL file content in which the debugging breakpoint or error occurs should be able to display the content of the remote file in the host machine as if the file is a local file and the debugger can function fully as if it is debugging a local AL object file.
4. Actual behavior
A clear and concise description of what happened accompanied by images, animations, or a link to a video showing the issue occurring
Related to Step (4):
When publishing/downloading symbols for the first time, the request for developer authentication is opened in the remote host machine, instead of the guest machine.
Related to step (5):
When I attach a debugger from a running BC Online session in the remote guest machine though, debugging can be attached, breakpoint can be captured, however, the .AL file in which the breakpoint occurs cannot be displayed. A one-line error stating "No content available." appears.
5. Versions:
AL Language extension for Microsoft Dynamics 365 Business Central
Final Checklist
Please remember to do the following:
Search the issue repository to ensure you are reporting a new issue
Reproduce the issue after disabling all extensions except the AL Language extension
Simplify your code around the issue to better isolate the problem