You will have to make the changes in X++ code and compile it, in order to make it available for further debugging, if required. Also, you can’t alter the code while debugging in Visual Studio. First off, if you want to step into another method or methods during the debugging process, you will need to have them pre-loaded (opened) in your Visual Studio IDE before you can actually attach the process. There are a few things that should keep in mind though while debugging AIF Services in Dynamics AX 2012. Now, make the service call from the client application and the control will eventually stop over the break point.Wait for until the code is attached to the process and all the relevant files and debugging symbols have been loaded into the memory. Then select ‘Ax32Serv.exe’ and press ‘Attach’. For this, select Debug menu > Attach to Process. Since AIF Services code is compiled into CIL (Common Intermediate Language) and run on the server, to debug it you’ll need to attach the debugger to the server (Ax32Serv.exe) process.Add a breakpoint to the code line that you’re interested in. Expand the methods given here and open the method that you want to debug. Next, open Visual Studio and in the Application Explorer pane expand the AOT (Application Objects Tree) and navigate to the AIF Service. You can install it from the Microsoft Dynamics AX CD by choosing Developer Tools > Visual Studio Tools. The AX Application Explorer is a Visual Studio add-on that is used browse the AX AOT (Application Objects Tree) within Visual Studio. You’ll also need Dynamics AX Application Explorer component installed as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |