What Will I Learn?

✓ Apply DIP and use IoC-Containers for Dependency Injection to come up with improved Architecture

✓ Set up IoC-Frameworks

View Curriculum

Available Licences

Personal: watch online on udemy.com.
Download: watch on any device.

Requirements

  • Solid experience in C#

Description

Teaching Approach

No fluff, no ranting, no beating the air. I esteem your time. The course material is succinct, yet comprehensive. All the important concepts are covered. Particularly important topics are covered in-depth. For absolute beginners, I offer my help on Skype absolutely free, if requested.

Take this course, and you will be satisfied.

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 don’t understand what is DI and IoC-Containers.

Content and Overview

This course is aimed at all kind of developers. It provides solid theoretical base reinforced by practical material.

The course covers:

  • Introduction to Inversion of Control:
    Dependency Inversion Principle (DIP), Inversion of Control (IoC), Dependency Injection (DI),
    Dependencies and their types, Pure DI and IoC-Containers, Service Locator
  • The Architectural Implications of Dependency Injection
  • DI-related Anti-Patterns & Refactorings:
    Control Freak, Hidden Dependencies, Temporal Coupling,
    Constructor Over-Injection and how to avoid it,
    Ambient Context, Facade Service, Property Injection vs Bastard Injection, Cyclic Dependencies
  • Refactoring Example of an existing code base applying Dependency Injection
  • How to reap the fruits of DI
  • DI-Containers (IoC-Containers):
    Overview, Unity, Late Binding with Unity, Aspect-Oriented Programming (AOP), Interception vs Pure DI vs AOP Tools,
  • Setting up a bootstrapper with Unity, Autofac and Castle.Windsor

Who is the target audience?

  • Any C# developer who wants to learn about Dependency Injection and IoC-Framework 

Curriculum

  • How to Ask Questions
  • Download Source Code and Slides
  • Outline
  • Definition of DIP
  • Dependencies
  • Volatile and Stable Dependencies
  • Definitions of IoC and DI
  • DIP Violation Demo
  • Refactoring to a Better Design Applying Dependency Injection
  • Dependency Injection Techniques
  • Architectural Implications
  • Common Smells of DIP Violation
  • Conclusion
  • Outline
  • Pure DI and IoC-Containers
  • Building a Simple IoC-Container
  • Service Locator Design Pattern
  • Demo With an IoC-Container
  • Conclusion
  • Outline
  • Control Freak
  • Hidden Dependencies with Service Locator
  • Temporal Coupling and Constructor Injection
  • Constructor Over-Injection
  • Facade Service
  • Ambient Context
  • Property Injection VS Bastard Injection
  • Cyclic Dependencies
  • Conclusion
  • Outline
  • Application Overview
  • Data Access and Models
  • UI-Side
  • The Problem of Tight Coupling
  • Refactoring Process
  • Isolating the Bootstrapper
  • Consequences
  • Conclusion
  • Outline
  • Application Overview
  • Data Access and Models
  • UI-Side
  • The Problem of Tight Coupling
  • Refactoring Process
  • Isolating the Bootstrapper
  • Consequences
  • Conclusion
  • Outline
  • Overview of DI-Containers
  • Unity DI-Framework
  • Late Binding with Unity
  • Aspect-Oriented Programming (AOP)
  • Demonstration of the Problem of Boilerplate Code
  • Implementing AOP by Intercepting
  • Interception vs Pure DI vs AOP Tooling
  • Autofac and Castle.Windsor DI-Containers
  • Problems Related to DI-Containers
  • Conclusion
  • BONUS Lecture