Can't open my App extension PageExt and TableExt in .dal from symbols package

[Magicrevette]

Hello,

1. Describe the bug
I'm on Business Centre 19.2 On-premise. I have compiled and published my app on my server. Then, from another project on VSCode, I've download the symbols from my instance. I got the standard Microsoft .app and my extension .app. When I open standard objects from Base App or System App (with Go To Definition, or from the list of objects from the package), they open in .dal. When I do this with the PageExt and TableExt objects of my .app, they open in .al and not in .dal. Because of this, the breakpoints I place in my page and table extensions don't work when I debug.

2. To Reproduce
Steps to reproduce the behavior:

With the command AL:Go!, create a new project. Set your launch.json to an instance On-Premise where you have published an app on. Download Symbols. Double-click on the package of your .app, search for any table of page extension, and open it (with a double-click, or Right-click > Go To Definition). It will open th object in .al and not in .dal. Put a breakpoint in it, and press ctrl+shift+f5 to debug without publishing. Your breakpoint will never be met.

3. Expected behavior
When I download my app package from Download Symbols, I expect to be able to open my table and page extension in .dal to put fonctional breakpoints in them.

4. Actual behavior

5. Versions:

• AL Language: v8.2.552672
• Visual Studio Code: 1.63.1
• Business Central: 19.2 On-Premise
• List of Visual Studio Code extensions that you have installed: AL Language, Al Object Designer, AZ AL Dev Tools/Al Code Outline, Bracket Pair Colorizer, Powershell, vscode-icons, Waldo's CRS AL Language Extension.

Thank you, have a nice day.

Pierre

[kalberes]

Hi,
Are you trying to go to definition through the AZ DevTools? What does this mean: "Double the package of your .app,"?
We do not control how gotodef was implemented by external tools?
What is that al file? Is that part of your project that you have published?
If you have the project which was published, why don't you open and debug that one?
Or you want a scenario just to debug your published app through a "Hello World" as symbols?. That should work too unless you have restricted it with the resourceExposure policy.

[Magicrevette]

Hello,
"Double the package of your .app," : it was a typo, sorry. I meant "double-click on the package of your .app".
Indeed, I want a scenario just to debug my published app through 'Hello World' as symbols. But When I do that, I can't open the table and page extensions of my app in .dal to put breakpoints in them. I want this scenario because I don't want an editable version of the projet to be on this server.

[kalberes]

Can you go to definition within the Al file that defines the reference ? Is your package published with debugging and IncludeSourceInSymbols resource exposure policy set to true? If not you won't be able to go to definition

[Magicrevette]

My package is published with these parameter :

"resourceExposurePolicy": {
"allowDebugging": true,
"allowDownloadingSource": true,
"includeSourceInSymbolFile": true
}

I don't understand when you say : "Can you go to definition within the Al file that defines the reference ?" What do you mean by that ?

[kalberes]

I mean open the AL file where you have a reference to your Page extension (or create one and define it) and issue a gotodefinition from there.

[thloke]

This issue has been closed because it needs more information and has not had recent activity. Please open a new issue if you believe this has not been resolved and reference the current issue.