7.2 KiB
:::moniker range=">= aspnetcore-3.0 < aspnetcore-8.0"
By Shadi Alnamrouti, Rick Anderson, and Steve Smith
ASP.NET Core MVC controllers request dependencies explicitly via constructors. ASP.NET Core has built-in support for dependency injection (DI). DI makes apps easier to test and maintain.
View or download sample code (how to download)
Constructor injection
Services are added as a constructor parameter, and the runtime resolves the service from the service container. Services are typically defined using interfaces. For example, consider an app that requires the current time. The following interface exposes the IDateTime service:
The following code implements the IDateTime interface:
Add the service to the service container:
For more information on xref:Microsoft.Extensions.DependencyInjection.ServiceCollectionServiceExtensions.AddSingleton*, see DI service lifetimes.
The following code displays a greeting to the user based on the time of day:
Run the app and a message is displayed based on the time.
Action injection with FromServices
The xref:Microsoft.AspNetCore.Mvc.FromServicesAttribute enables injecting a service directly into an action method without using constructor injection:
Access settings from a controller
Accessing app or configuration settings from within a controller is a common pattern. The options pattern described in xref:fundamentals/configuration/options is the preferred approach to manage settings. Generally, don't directly inject xref:Microsoft.Extensions.Configuration.IConfiguration into a controller.
Create a class that represents the options. For example:
Add the configuration class to the services collection:
Configure the app to read the settings from a JSON-formatted file:
The following code requests the IOptions<SampleWebSettings> settings from the service container and uses them in the Index method:
Additional resources
-
See xref:mvc/controllers/testing to learn how to make code easier to test by explicitly requesting dependencies in controllers.
-
Replace the default dependency injection container with a third party implementation.
:::moniker-end
:::moniker range="< aspnetcore-3.0"
By Shadi Namrouti, Rick Anderson, and Steve Smith
ASP.NET Core MVC controllers request dependencies explicitly via constructors. ASP.NET Core has built-in support for dependency injection (DI). DI makes apps easier to test and maintain.
View or download sample code (how to download)
Constructor injection
Services are added as a constructor parameter, and the runtime resolves the service from the service container. Services are typically defined using interfaces. For example, consider an app that requires the current time. The following interface exposes the IDateTime service:
The following code implements the IDateTime interface:
Add the service to the service container:
For more information on xref:Microsoft.Extensions.DependencyInjection.ServiceCollectionServiceExtensions.AddSingleton*, see DI service lifetimes.
The following code displays a greeting to the user based on the time of day:
Run the app and a message is displayed based on the time.
Action injection with FromServices
The xref:Microsoft.AspNetCore.Mvc.FromServicesAttribute enables injecting a service directly into an action method without using constructor injection:
Access settings from a controller
Accessing app or configuration settings from within a controller is a common pattern. The options pattern described in xref:fundamentals/configuration/options is the preferred approach to manage settings. Generally, don't directly inject xref:Microsoft.Extensions.Configuration.IConfiguration into a controller.
Create a class that represents the options. For example:
Add the configuration class to the services collection:
Configure the app to read the settings from a JSON-formatted file:
The following code requests the IOptions<SampleWebSettings> settings from the service container and uses them in the Index method:
Additional resources
-
See xref:mvc/controllers/testing to learn how to make code easier to test by explicitly requesting dependencies in controllers.
-
Replace the default dependency injection container with a third party implementation.
:::moniker-end