From 60be8995d4878b3c21ed074d24ab0f05dc6c10f3 Mon Sep 17 00:00:00 2001 From: Steve Dougherty Date: Thu, 21 May 2026 13:28:57 -0400 Subject: [PATCH] Add missing quote to example configuration --- docs/core/tools/dotnet-package-update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/tools/dotnet-package-update.md b/docs/core/tools/dotnet-package-update.md index b011c37e2a454..725b7f9f03b9d 100644 --- a/docs/core/tools/dotnet-package-update.md +++ b/docs/core/tools/dotnet-package-update.md @@ -34,7 +34,7 @@ Using `--vulnerable` also does an implicit restore to find NuGetAudit warnings. However, if your project uses `WarningsAsErrors` or `TreatWarningsAsErrors`, NuGet's restore warnings can cause restore to fail, preventing the update from completing. We recommend taking advantage of MSBuild conditions and environment variables as a workaround until [this feature request](https://github.com/NuGet/Home/issues/14311) is implemented. -For example, set `true` in your project, and then on most Linux and Mac shells you can run `CustomCondition=true dotnet package update`. On Windows Command Prompt and PowerShell, you will need to set the environment variable, run dotnet package update, then unset the environment variable as three separate commands. ## Arguments