Thanks for the response and pointing out some confusing issues in it.
Here IoC is a general concept while DI is an implementation merely using IoC concept.
Inversion of Control vs Dependency Injection
According to the paper written by Martin Fowler, inversion of control is the principle where the control flow of a…
I will look into ‘Poor Man’s DI’ as you mentioned as I haven’t run into that. By the first glance it looks like it is an exception but most of the time Dependency Inversion Principle -> IoC -> DI holds true. I gather that conceptually DI, IoC are generic terms but more beneficial when working together. Please refer to these articles with similar idea.
Inversion of Control - An Introduction with Examples in .NET
An introduction to Inversion of Control, using the Dependency Injection and Service Locator patterns, with simple…
Understanding Inversion of Control, Dependency Injection and Service Locator
So many developers are confused about the the term Dependency Injection (DI). The confusion is about terminology…
Inversion of Control, Dependency Injection and Service Locator in C#
C# Tutorials,ASP.net Tutorials,ASP.net Core,Entity Frameowrk Core,Interview questions,csharp tutorials, c-sharp…
As per Service Locator I had not dig into that very much but basically service locator pattern asks for dependencies from ServiceLocator class and not directly from concrete implementation. Here the using class is not aware of the concrete implementation and the control is passed to ServiceLocator (Hence pretty much the idea of Inverting of control)
Confused over using IOC container, service locator and factory
If possible, you should always go with dependency injection, since it has a few clear strength. With UI technologies…
Please look into these points and clarify if there’s anything. (Point out anything that needs to be changed since I’m amateur writer.)