CHAPTER 1 - Introduction to X++
CHAPTER 2 - X++ Control Statements
CHAPTER 3 - Objects and Classes
CHAPTER 4: Accessing the Database
CHAPTER 5: Exception Handling
CHAPTER 6: Security for Developers
Lesson 10 – Eventing
The eventing feature lets the user use a publisher and subscriber model when modifying Microsoft Dynamics AX. Events can be modeled in the AOT or be used as a programming construct and can be handled in either X++ code or in managed code.
The Microsoft Dynamics AX architecture includes application layers that can be customized in upper layers. For example, when Microsoft ships a class in the SYS layer, a developer can change the class in an upper layer such as the CUS layer. At run time, the X++ language engine use the version of code in the highest layer. You can use to decouple the custom code from the implementation of the underlying layer. The application developers from a lower level can freely change the implementation at any time without the developers of the upper layer having to make any changes to their code, as long as the modified code author raises the same events in the same order. Basically, the application developers build an API enabling customization through events.