Skip to content

Ioc container

Jump to bottom Edit New page
Bianca Ghiurutan edited this page Feb 7, 2018 · 4 revisions

IoC Container

To understand what an IoC (Inversion of Control) Container is, we first need to understand what Dependency Injection is.

Dependency Injection is a design pattern used for making decoupled software modules (classes, generally speaking). DI pattern implements Dependency Inversion Principle, which is the D in SOLID.

IoC (Inversion of Control) Container (a.k.a. DI Container) is a framework for implementing automatic dependency injection. It manages object creating and its lifetime and also injects dependencies to the class.

In conclusion, an IoC Container implements the DI pattern for us, omitting the need to manually create our own code for decoupling our classes.

Licensed under Apache 2 License

Contents

  1. Home
  2. Why Use Ninject
  3. Getting Started
  4. Dependency Injection By Hand
  5. Dependency Injection With Ninject
  6. Injection Patterns
  7. Multi Injection
  8. Object Scopes
  9. Modules and the Kernel
  10. Providers, Factory Methods and the Activation Context
  11. The Activation Process
  12. How Injection Works
  13. Contextual Binding
  14. Conventions-Based Binding

Clone this wiki locally