![]() ![]() You can drag a variable here from the Code window or Window, you can inspect variables without the scope limitations of the Indicates the tier on which the code is executed. Window and updates the local Variables window. Shows the code path followed to arrive at a particular execution point.Ĭlicking a line in the Call Stack window opens the code in the Code ![]() If your class doesn’t explicitly extend object (the base class of all classes), you must add a new method named toString, returning str and taking no parameters, to implement this functionality. You can change the defaults by overriding the toString method. For a class, the defaults are New and Null. Modify the value of a variable by double-clicking the value.Ī developer, you might want to provide more information in the valueįield than what is provided by default. Variable is changed during execution stepping, it is marked in red.Įach variable is shown associated with a client or server icon. Variables window shows the name, value, and type of each variable. Member variables make sense only on classes, and they show the class member variables. The global classes that are always instantiated: Appl, Infolog, ClassFactory, and VersionControl. Variables in scope at the current execution point. Local, global, and member variables are shown. What you expected or if you want to repeat a step. This pointer is particularly useful if the execution path isn’t You can drag the next-statement pointer in the left 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. While variables and other aspects are inspected. You can control execution one step at a time Main window in the debugger initially shows the point in the code whereĪ breakpoint was hit. This means that your breakpoints are not cleared when you close DynamicsĪX and that other Dynamics AX components can access them and break 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ĭatabase table. You can enable or disable a breakpoint by pressing Ctrl F9. A breakpoint on the last brace will never be Statement, however, the breakpoint will be triggered on the next X If you set a breakpoint on a line without an X You can set a breakpoint onĪny line you want. Set and remove breakpoints by pressing F9. ![]() If you do, execution will stop when it hits aīreakpoint, and users will experience a hanging client. Recommend that you do not enable any of the debugging capabilities in a The latter is useful for debugging incoming Web requests. Two check boxes on the Developer tab: Enable User Breakpoints Forĭebugging Code Running In The Business Connector or Enable Globalīreakpoints For Debugging Code Running In The Business Connector OrĬlient. Necessary), and select the check box labeled Enable Global BreakpointsĮnterprise Portal and Business Connector, open the Microsoft DynamicsĪX Configuration utility under Start\Administrative Tools. Necessary), and select the check box labeled Enable Breakpoints To Debugīatch jobs, open the Microsoft Dynamics AX Server Configuration utility The AOS, open the Microsoft Dynamics AX Server Configuration utility You must enable debugging for each component as follows:ĭynamics AX client, click the Microsoft Dynamics AX drop-down menu, The debugger starts automatically when any You set breakpoints by using the X code editor in the Microsoftĭynamics AX client. The debugger to start, a breakpoint must be hit during execution of X Ĭode. Īs a stand-alone application, the debugger allows you to debug X inĪny of the Dynamics AX components in the following list: The debugger is a stand-alone application, not part of theĭynamics AX shell like the rest of the tools. Like most development environments, MorphX features aĭebugger. ![]()
0 Comments
Leave a Reply. |