Book Image

Dependency Injection in .NET Core 2.0

By : Marino Posadas, Tadit Dash
Book Image

Dependency Injection in .NET Core 2.0

By: Marino Posadas, Tadit Dash

Overview of this book

<p><span id="description" class="sugar_field">.NET Core provides more control than ever over web application architectures. A key point of this software architecture is that it's based on the use of Dependency Injection as a way to properly implement the Dependency Inversion principle proposed in the SOLID principles established by Robert C. Martin</span>.</p> <p><span id="description" class="sugar_field">With the advent of .NET Core, things have become much simpler with Dependency Injection built into the system. This book aims to give you a profound insight into writing loosely-coupled code using the latest features available in .NET Core. It talks about constructors, parameter, setters, and interface injection, explaining in detail, with the help of examples, which type of injection to use in which situation. It will show you how to implement a class that creates other classes with associated dependencies, also called IoC containers, and then create dependencies for each MVC component of ASP.NET Core. You'll learn to distinguish between IoC containers, the use of Inversion of Control, and DI itself, since DI is just a way of implementing IoC via these containers. You'll also learn how to build dependencies for other frontend tool such as Angular. You will get to use the in-built services offered by .NET Core to create your own custom dependencies.</span></p> <p><span class="sugar_field"><span id="description" class="sugar_field">Towards the end, we'll talk about some patterns and anti-patterns for Dependency Injection along with some techniques to refactor legacy applications and inject dependencies.</span></span></p>
Table of Contents (18 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Composition over Inheritance


This topic is very interesting and is discussed online in many websites and blogs. As the topic headline says Composition is preferred over Inheritance, we need to understand why it is so important by identifying the problems. The better the design from the beginning of your software development, the better the maintainability and reuse.

Inheritance and Composition are two pillars of OOPs concepts. Unless they are used wisely according to your architecture, they will create problems in the future when you start adding complexity to your application.

We have already discussed Composition, now, let's discuss Inheritance before we move towards the main topic of discussion.

Inheritance

As the name suggests, the act of acquiring or deriving some behavior from someone is called Inheritance. In the programming world, when a certain class is inherited from another class, it creates an Inheritance. Some basic examples are written as follows:

  • A car is a vehicle. The vehicle...