From df6df4c651f6617b56bdbd2cba3e9f16fd21c961 Mon Sep 17 00:00:00 2001 From: Daniel Plaisted Date: Tue, 22 Nov 2022 08:24:08 -0500 Subject: [PATCH] Fix incomplete sentence --- accepted/2022/simplify-output-paths.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/accepted/2022/simplify-output-paths.md b/accepted/2022/simplify-output-paths.md index 40a25bd50..7a58a55ac 100644 --- a/accepted/2022/simplify-output-paths.md +++ b/accepted/2022/simplify-output-paths.md @@ -26,7 +26,7 @@ Projects targeting .NET 8 and higher will by default use a new output path forma - Output Type - Such as `build`, `publish`, `obj`, or `packages` - Pivots - This will at minimum be the `Configuration`, such as `Debug` or `Release`. Other pivots such as `TargetFramework` or `RuntimeIdentifier` may also be included, and the pivots will be joined by the underscore (`_`) character - `TargetFramework` will be included in the folder name if the project is multi-targeted (`TargetFrameworks` is non-empty), or if the `TargetFramework` property was set via the command line (ie is a global property) - - `RuntimeIdentifier` will be included in the folder name if it was explicitly set (either in a project file or on the command line). If it is set automatically by the SDK (for example because `SelfContained` was set) + - `RuntimeIdentifier` will be included in the folder name if it was explicitly set (either in a project file or on the command line). If it is set automatically by the SDK (for example because `SelfContained` was set), then the `RuntimeIdentifier` will not be included in the folder name. Some examples: