From b789a30c84aaaff2435ad74a0caa5340847df7bd Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Tue, 6 Aug 2019 07:31:40 -0500 Subject: [PATCH] Fix API link (#13685) --- aspnetcore/fundamentals/dependency-injection.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/fundamentals/dependency-injection.md b/aspnetcore/fundamentals/dependency-injection.md index 705e5d6fc3..b9111e7d04 100644 --- a/aspnetcore/fundamentals/dependency-injection.md +++ b/aspnetcore/fundamentals/dependency-injection.md @@ -5,7 +5,7 @@ description: Learn how ASP.NET Core implements dependency injection and how to u monikerRange: '>= aspnetcore-2.1' ms.author: riande ms.custom: mvc -ms.date: 07/24/2019 +ms.date: 08/06/2019 uid: fundamentals/dependency-injection --- # Dependency injection in ASP.NET Core @@ -169,7 +169,7 @@ Scoped lifetime services () are created the first time they're requested (or when `Startup.ConfigureServices` is run and an instance is specified with the service registration). Every subsequent request uses the same instance. If the app requires singleton behavior, allowing the service container to manage the service's lifetime is recommended. Don't implement the singleton design pattern and provide user code to manage the object's lifetime in the class. +Singleton lifetime services () are created the first time they're requested (or when `Startup.ConfigureServices` is run and an instance is specified with the service registration). Every subsequent request uses the same instance. If the app requires singleton behavior, allowing the service container to manage the service's lifetime is recommended. Don't implement the singleton design pattern and provide user code to manage the object's lifetime in the class. > [!WARNING] > It's dangerous to resolve a scoped service from a singleton. It may cause the service to have incorrect state when processing subsequent requests.