Chapter 1: X++ Unit Test Framework
Chapter 2: Working with Data
Chapter 3: Classes
Chapter 4: Forms
Chapter 5: Visual Studio Integration
Chapter 6: Workflow
Lesson 5 : Visual Studio Debugging Experience for X++
Visual Studio Debugging Experience for X++
With a tight integration between X++ and Visual Studio, an integrated debugging experience is essential for developers. It is possible to use the Visual Studio debugger to debug managed code that is called from X++. The opposite is also true. X++ code that is called from managed code can be debugged using the Microsoft Dynamics AX debugger.
After you create a project in Microsoft Visual Studio and add it to the model store, you can set the project debug properties and use Visual Studio to start debugging your code. Although you start debugging in Visual Studio, some debugging is still done in the Microsoft Dynamics AX Debugger. For more information, see Walkthrough: Using the Debug Properties When Debugging Managed Code.
The debug properties are properties on a managed code project. These properties work together to enable you to debug both X++ code and managed code from Visual Studio. The Debug Target property specifies which Microsoft Dynamics AX process Visual Studio should attach to when you are debugging. The Startup Element property specifies the X++ code that will be called by the debugger after it attaches to the Microsoft Dynamics AX process.
Debug Target Property
The Debug Target property enables you to designate which Microsoft Dynamics AX process Visual Studio should attach to when you debug.
- When this property is set to Client, the debugger attaches to the process Ax32.exe.
- When this property is set to Server, the debugger attaches to the process Ax32Serv.exe.
- When this property is set to SSRS, the debugger attaches to the process ReportingServicesService.exe.
Startup Element Property
The Startup Element property enables you to specify a Microsoft Dynamics AX job, menu item, class, or form that will run after Visual Studio attaches to the appropriate process.
You can manually modify the Startup Element property by providing the path of the application element in the Application Object Tree (AOT), or you can right-click an element in Application Explorer and select Set as startup element.