From a5860bafdd384e6810d670eb5fc823ab8b35e1ea Mon Sep 17 00:00:00 2001 From: danroth27 Date: Mon, 14 Dec 2015 16:31:52 -0800 Subject: [PATCH] Property injection is not supported by default --- aspnet/fundamentals/dependency-injection.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnet/fundamentals/dependency-injection.rst b/aspnet/fundamentals/dependency-injection.rst index 6811179151..9005f88fcf 100644 --- a/aspnet/fundamentals/dependency-injection.rst +++ b/aspnet/fundamentals/dependency-injection.rst @@ -19,7 +19,7 @@ When classes are designed with DI in mind, they are more loosely coupled because When a system is designed to use DI, with many classes requesting their dependencies via their constructor (or properties), it's helpful to have a class dedicated to creating these classes with their associated dependencies. These classes are referred to as *containers*, or more specifically, `Inversion of Control (IoC) `_ containers or Dependency Injection (DI) containers. A container is essentially a factory that is responsible for providing instances of types that are requested from it. If a given type has declared that it has dependencies, and the container has been configured to provide the dependency types, it will create the dependencies as part of creating the requested instance. In this way, complex dependency graphs can be provided to classes without the need for any hard-coded object construction. In addition to creating objects with their dependencies, containers typically manage object lifetimes within the application. -ASP.NET 5 includes a simple built-in container (represented by the ``IServiceProvider`` interface) that supports constructor and property injection by default, and ASP.NET makes certain services available through DI. ASP.NET's container refers to the types it manages as *services*. Throughout the rest of this article, *services* will refer to types that are managed by ASP.NET 5's IoC container. You configure the built-in container's services in the ``ConfigureServices`` method in your application's ``Startup`` class. +ASP.NET 5 includes a simple built-in container (represented by the ``IServiceProvider`` interface) that supports constructor injection by default, and ASP.NET makes certain services available through DI. ASP.NET's container refers to the types it manages as *services*. Throughout the rest of this article, *services* will refer to types that are managed by ASP.NET 5's IoC container. You configure the built-in container's services in the ``ConfigureServices`` method in your application's ``Startup`` class. .. note:: Martin Fowler has written an extensive article on `Inversion of Control Containers and the Dependency Injection Pattern `_. Microsoft Patterns and Practices also has a great description of `Dependency Injection `_.