Debug in Interpreted Mode Your X++ Code that Runs as .NET CIL [AX 2012]
Updated: October 14, 2011
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
In some cases you can debug your X++ code in interpreted mode even where the code is typically compiled to run as .NET Framework CIL. To activate this option, you clear a check box in the Options window of the Microsoft Dynamics AX development workspace.
During development when you are frequently making code changes and retesting, it is sometimes more convenient to debug X++ in interpreted mode. This option is convenient in the following ways:
You can avoid regenerating the CIL after each X++ code change.
You can debug by using the Microsoft Dynamics AX debugger, instead of attaching the Microsoft Visual Studio debugger to the Application Object Server (AOS). This is important when multiple developers are sharing one AOS.
In some cases you can debug your X++ code in interpreted mode even where the code is typically compiled to run as .NET Framework CIL. But in other cases you cannot, and you can only debug in CIL mode. The following table lists some cases in each category.
Yes, the Execute business operations in CIL setting has an effect. You can debug X++ code in interpreted mode.
No, the Execute business operations in CIL setting is ignored. You must debug in CIL mode.