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)

WPF and Silverlight applications


Although Silverlight is a lighter version of Windows Presentation Foundation (WPF), these two frameworks are so similar that they can be treated the same way in terms of DI. Both frameworks offer a single startup location for the application in their App.xaml file, which can be used as the Composition Root. The view engine for both frameworks is based on Extensible Application Markup Language (XAML) and they both support Model-View-ViewModel (MVVM) architecture.

In this section we will implement the Northwind scenario using MVVM pattern which can be applied to either WPF or a Silverlight application. In MVVM, the application consists of the following key parts:

  • Model: The domain Models that represent business entities, and we have already created them in our domain layer.

  • View: A XAML UI file which is usually a Window or a User Control with minimal or no code behind.

  • ViewModel: As the name suggests, it is a Model for the View. It contains the presentation...