

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. Running the application with debug support enabled also noticeably affects performance. If you do, execution will stop when it hits a breakpoint, and the client will stop responding to users. It is recommended that you do not enable any of the debugging capabilities in a live environment. This is necessary to prohibit unauthorized debugging, which could expose sensitive data, provide a security risk, or impose unplanned service disruptions.
BUTTON TO OPEN MORPHX DYNAMICS AX WINDOWS
This is normally ensured by using setup, but if you did not set up AX 2012 by using your current account, you need to do this manually through Edit Local Users And Groups in Windows Control Panel.
BUTTON TO OPEN MORPHX DYNAMICS AX CODE

You set breakpoints by using the X++ code editor in the Development Workspace. NET.” Enabling debuggingįor the debugger to start, a breakpoint must be hit when X++ code is executed.

As a stand-alone application, the debugger allows you to debug X++ in any of the following AX 2012 components:įor other debugging scenarios, such as web services, Microsoft SQL Server Reporting Services (SSRS) reports, and Enterprise Portal web client, see Chapter 3, “AX 2012 and. The debugger is a stand-alone application, not part of the AX 2012 shell like the rest of the tools mentioned in this chapter. Like most development environments, MorphX features a debugger.
