Friday, September 1, 2017

How to Debug batch jobs and service operations in Dynamics AX 2012

All batch jobs and service operations now run in managed code (IL) and require different 
debugging steps.  Rather than setting breakpoints within X++, you need to set them within
the IL code that corresponds to the X++ code and debug in Visual Studio.
1) Open Visual Studio as 'administrator' and attach the debugger to the Ax32Serv.exe process.
2) Note that it may also be necessary to change the ‘Attach to’ selection to
‘Managed (v4.0) code’ and make sure “just my code” is unchecked in 
VS: tools->options->debugging->General
3) Once done, open up the file you want to debug in Visual Studio. 
All of the X++ code is compiled into IL and can be found in the 
following directory after deployment: 
..\Program Files\Microsoft Dynamics Ax\6.0\Server\AxaptaDev\Bin\XppIL\source\
4) Set a breakpoint in the file you opened.
5) Go to Ax and run the process in batch mode, or execute the service operation.
 This will end up hitting your breakpoint, provided you set it in the right place.


If you make some changes to X++ code and want those changes reflected in the 
generated IL code, you need to do the following AFTER you have compiled the X++ code.
Once done, your changes will be reflected in your next debugging session:

Source:

No comments:

Post a Comment

D365 Extensions: Extend the validateField Method on a Table

In this post I will going to show you, how to extend the validateField method on a table. As example I used the SalesLine, where I will ...