MaricaPiazzalunga
commented
3 years ago I have the same issue with BC version "17.1" and the version of AL Object Designer is "0.2.4". I set a breakpoint in the .al file loaded by AL Object Designer. After that, when a start the debugger from VSCode, the debugger does not break on the breakpoints that I set. Rather, in addition to this, when the debugger starts VSCode asks me to save the file ".al", leaded by AL Object Designer, where I put the breakpoint. Even if I save the file in the project folder, the debugger does not break on the breakpoint. While, if I jump to the object with the "Go to definition" from an AL file in my workspace, AL Object Designer opens the object file, I set the breakpoint and when I start the debugger, it wll break to the breakpoint correctly.
Any fix or reason of this behavior?
We have an onpremise AL app that depends on multiple third party extensions and use AL Object Designer extensively to jump around the objects defined in those parent dependency apps. When we "view" an Application symbol object from AL Object Designer, the .dal gets downloaded will full source code (all our dependency apps are showmycode=true).
VS Code allows us to set breakpoints into those .dal files that AL Object Designer produces, however, the breakpoints do not get hit when the debugger launches.
However, if I jump to an object definition from an AL file in my workspace: the .dal loads up, I can set breakpoints into it, and the debugger will break into those BP's
Any reason why .dal debugging doesn't work for .dal files generated by AL Object Designer?
BC Version: Version: NA Business Central 16.2 (Platform 16.0.13440.13772 + Application 16.2.13779.0) "AL Language" version: 5.0.288712 "AL Object Designer" version: 0.2.2