Inversion of control framework for Dynamics Ax

We all agree that tightly coupled code is bad because is a nightmare to maintain when the application is growing bigger and bigger (and an ax application is always big!). If a class depends on another class, then we need to change one class if something changes in that dependent class. We should always try to write loosely coupled class.

The solution is Dependency injection.

The problem, is that in Microsoft Dynamics Ax we don’t have any dependency injection container and that make dependency injection less appealing.

But I come from c# development where DI is a standard, so I tried to find a solution, might not be perfect, but I taught that sharing with the community my experiment is a good way to get feedback on what I did.

Let’s begin (I suppose you are already familiar with DI before you continue…):

https://enricoariel.blogspot.com/2019/08/inversion-of-control-framework-for.html