Book Image

Mastering Ninject for Dependency Injection

By : Daniel Baharestani
Book Image

Mastering Ninject for Dependency Injection

By: Daniel Baharestani

Overview of this book

Dependency injection is an approach to creating loosely coupled applications. Maintainability, testability, and extensibility are just a few advantages of loose coupling. Ninject is a software library which automates almost everything that we need in order to implement a dependency injection pattern. Mastering Ninject for Dependency Injection will teach you everything you need to know in order to implement dependency injection using Ninject in a real-life project. Not only does it teach you about Ninject core framework features that are essential for implementing dependency injection, but it also explores the power of Ninject's most useful extensions and demonstrates how to apply them. Mastering Ninject for Dependency Injection starts by introducing you to dependency injection and what it's meant for with the help of sufficient examples. Eventually, you'll learn how to integrate Ninject into your practical project and how to use its basic features. Also, you will go through scenarios wherein advanced features of Ninject, such as Multi-binding, Contextual binding, providers, factories and so on, come into play. As you progress, Mastering Ninject for Dependency Injection will show you how to create a multilayer application that demonstrates the use of Ninject on different application types such as MVC, WPF, WCF, and so on. Finally, you will learn the benefits of using the powerful extensions of Ninject.
Table of Contents (12 chapters)

Multi binding and contextual binding


In the previous chapter, we saw how Ninject can resolve dependency types in single binding situations, that is, each service type is bound only to a single implementation type. However, there are situations where we need to bind an abstract service type to multiple implementations, which is called as multi binding. Multi binding has two scenarios. The first one is the plugin model implementation and the other one is contextual binding, which we will discuss in this section.

Implementing the plugin model

The plugin model allows an application to be extremely extensible without modifying its source code. In the following example, we will implement a Music Player application, which uses codec plugins in order to support different music formats. The application comes out with two built-in codecs, and it is possible to add more plugin codecs and extend the formats that our player application supports. Please note that as we try to keep the application as simple...