Software Architecture: Dependency Injection for C# Devs

Build a solid foundation in software architecture applying Dependency Injection with IoC–Containers

In many of my courses I use techniques of Dependency Injection and each time students write me private messages saying that they don’t what it is and thus they don’t understand what’s going on in the course I teach. This is very unfortunate from the learning perspectives.

Dependency Injection is the set of techniques that allow to supply dependencies to objects. Actually, if you have ever passed dependencies via constructors, then you applied the so–called constructor injection. Dependency Injection (DI) is simple and difficult at the same time. On one hand, DI is comprised of simple techniques and on the other hand, when we need to bring DI to the next level, we need to make things more complicated using the so–called DI or IoC (Inversion of Control) Containers. These are the frameworks which perform dependency injection automatically. You just need to set one up in the application root (an extremely important notion which you’ll learn about in the course) and after that, it will resolve all the dependencies it knows about in the runtime.

If you still don’t understand what am I talking about, just believe me, you absolutely need to know about Dependency Injection. This course will tremendously improve your understanding of how software architectures emerge. So, this course is must watch for anyone who still doesn’t understand what is DI and IoC–Containers.