In the previous post I covered why CAB dependency injection is limited. Now let’s see why it is entangled with other stuff. There are several things I want to mention here.
First, in order to use CAB dependency injection, you will need a work item. Besides being the thing that knows how to build objects, work item is, well, everything. It can be run, it can be activated, it has “state”, and “status”, it can be saved, loaded, and the rumor goes, it corresponds to a use case.