What is the meaning of “inversion” in Dependency Inversion design principle?
I’m reading about design patterns. I know what this principle does.
How to maintain Dependency Inversion Principle with enums & custom types?
From what I understand two components A and B should only communicate with one another via an interface. Ideally this interface should be in its own separate assembly so that the client need not be loaded with the dependencies of any particular interface implementation.