Tracing and Debugging | Microsoft Dynamics AX 2012 R2 Services

Using the Microsoft Dynamics AX 2012 debugger

The Microsoft Dynamics AX 2012 debugger has long been the only debugging tool available for developers and is specially designed to debug X++ code running on both the Microsoft Dynamics AX client and the AOS. It cannot debug code running in CIL.

If services are running in CIL and the debugger is unable to debug them, how can it be useful? We'll take a look at two scenarios: debugging the SysOperation framework and testing service operations.

Debugging the SysOperation framework

Although the SysOperation framework uses services running in CIL, it still has components that run on the client. These components include:

The controller class
The UI builder class
The data contract, which includes the initialization and validation of the data

All of these have to be debugged using the Dynamics AX debugger. The only component that runs in CIL and has to be debugged using Visual Studio is the service operation. However, there is a way around this as follows:

In...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Microsoft Dynamics AX 2012 R2 Services

Microsoft Dynamics AX 2012 R2 Services

Overview of this book

Using the Microsoft Dynamics AX 2012 debugger

Debugging the SysOperation framework

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access