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.
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...