Fix casing for UTF8Output propery#11179
Merged
Merged
Conversation
A quick search of the SDK installation shows that all usages of this property use the 'Output' form, not 'OutPut'. This doesn't matter from a functionality perspective, but for consistency we should clean it up.
rainersigwald
approved these changes
Dec 20, 2024
JanKrivanek
approved these changes
Dec 23, 2024
This was referenced Jul 28, 2025
This was referenced Aug 4, 2025
This was referenced Aug 15, 2025
This was referenced Jun 28, 2026
This was referenced Jul 6, 2026
This was referenced Jul 13, 2026
[release/9.0]: Bump Microsoft.Build.Framework and Microsoft.Build.Utilities.Core
dotnet/efcore#38637
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A quick search of the SDK installation shows that all usages of this property use the 'Output' form, not 'OutPut'. This doesn't matter from a functionality perspective, but for consistency we should clean it up.
A community member noticed this, so why not fix it up?