I think the DI introduction could be more approachable to beginners. At a high level, the goal is that a class (e.g. controller) needs something that satisfies an interface. It doesn't care what the concrete type is, it wants someone else to handle that. The Dependency Resolver in ASP.NET MVC can allow you to register your dependency logic somewhere else.
I've found that the diagrams help some people and confuse others. It's best to focus on the goal a bit more, perhaps with some illustrations - a doctor calling out for a scapel, or a golfer asking his caddy for a club.
I think the DI introduction could be more approachable to beginners. At a high level, the goal is that a class (e.g. controller) needs something that satisfies an interface. It doesn't care what the concrete type is, it wants someone else to handle that. The Dependency Resolver in ASP.NET MVC can allow you to register your dependency logic somewhere else.
I've found that the diagrams help some people and confuse others. It's best to focus on the goal a bit more, perhaps with some illustrations - a doctor calling out for a scapel, or a golfer asking his caddy for a club.