![]() ![]() This pointer is particularly useful if the execution path isn’t what you expected or if you want to repeat a step. You can drag the next-statement pointer in the left margin. Each variable has a ScreenTip that reveals its value. The main debugger window shows the current X++ code. In the following subsections, we briefly describe the debugger’s various windows and some of its other features. Figure 1 shows the debugger opened to a breakpoint with all the windows enabled.įigure 1. You can control execution one step at a time while variables and other aspects are inspected. The main window in the debugger initially shows the point in the code where a breakpoint was hit. This means that your breakpoints are not cleared when you close Dynamics AX and that other Dynamics AX components can access them and break where you want them to. Each developer has his or her own set of breakpoints. For a list of all breakpoints, press Shift+F9.īreakpoints are persistent in the SysBreakpoints database table. You can enable or disable a breakpoint by pressing Ctrl+F9. ![]() A breakpoint on the last brace will never be hit. If you set a breakpoint on a line without an X++ statement, however, the breakpoint will be triggered on the next X++ statement in the method. You can set a breakpoint on any line you want. The debugger allows you to set and remove breakpoints by pressing F9. If you do, execution will stop when it hits a breakpoint, and users will experience a hanging client. We recommend that you do not enable any of the debugging capabilities in a live environment. The latter is useful for debugging incoming Web requests. Select one of two check boxes on the Developer tab: Enable User Breakpoints For Debugging Code Running In The Business Connector or Enable Global Breakpoints For Debugging Code Running In The Business Connector Or Client. Create a new configuration (if necessary), and select the check box labeled Enable Global Breakpoints To Debug X++ Code Running In Batch Jobs.įor Enterprise Portal and Business Connector, open the Microsoft Dynamics AX Configuration utility under Start\Administrative Tools. ![]() Create a new configuration (if necessary), and select the check box labeled Enable Breakpoints To Debug X++ Code Running On This Server.įor Batch jobs, open the Microsoft Dynamics AX Server Configuration utility under Start\Administrative Tools. On the Development tab, select When Breakpoint in the Debug Mode list.įor the AOS, open the Microsoft Dynamics AX Server Configuration utility under Start\Administrative Tools. In the Microsoft Dynamics AX client, click the Microsoft Dynamics AX drop-down menu, point to Tools and then Options. You must enable debugging for each component as follows: The debugger starts automatically when any component hits a breakpoint. You set breakpoints by using the X++ code editor in the Microsoft Dynamics AX client. įor the debugger to start, a breakpoint must be hit during execution of X++ code.As a stand-alone application, the debugger allows you to debug X++ in any of the Dynamics AX components in the following list: The debugger is a stand-alone application, not part of the Dynamics AX shell like the rest of the tools. Like most development environments, MorphX features a debugger.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |