Mastering Ninject for Dependency Injection

For .NET developers and architects, this is the ultimate guide to the principles of Dependency Injection and how to use the automating features of Ninject in the most effective way. Packed with examples, diagrams, and illustrations.

Key Features

• Create loosely coupled applications by implementing dependency injection using Ninject
• Learn how to design an enterprise application so as to maximize its maintainability, extensibility and testability
• Automate the process of dealing with the dependencies of your application and object lifetimes
• Address the cross-cutting concerns of your applications in the easiest way
• Full of real-life, step-by-step examples and clear code samples

Book Description

What you will learn

• Understand dependency injection, how it is different from similar patterns such as inversion of control, and the problems that it addresses
• Set up Ninject in an application and configure it either using XML or programmatically
• Learn how to control object life-time by configuring object scopes
• Wire up abstract service types to concrete implementations using bindings
• Create plugins to add new features to compiled applications dynamically
• Use Ninject in different application types such as Win Forms, Web Forms, WPF, Silverlight, ASP.NET MVC, and WCF
• Inject common loggers such as log4net and NLog automatically into application components
• Test application units and automate the injection of mock objects by integrating Ninject with common mock frameworks (for example Moq or Rhino Mock)
• Register hundreds of bindings in a single line of code using the Convention configuration
• Inject the implementation of cross-cutting concerns such as logging, exception handling, or caching by interception

Who this book is for

Mastering Ninject for Dependency Injection is aimed at software developers and architects who wish to create maintainable, extensible, testable, and loosely coupled applications. Since Ninject targets the .NET platform, this book is not suitable for software developers of other platforms. Being familiar with design patterns such as singleton or factory would be beneficial, but no knowledge of dependency injection or IoC is assumed.