Pass NoWarn to external MSBuild processes
#12647
Merged
Conversation
This file contains 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
|
@dotnet-policy-service agree company="Enscape" |
|
Fixed |
TomEdwardsEnscape
force-pushed
the
fixes/nowarn
branch
from
93ec8dd to
7a47cb4
Compare
TomEdwardsEnscape
force-pushed
the
fixes/nowarn
branch
from
7a47cb4 to
fa40a32
Compare
|
You can test this PR using the following package version. |
maxkatz6
approved these changes
Sep 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change allows users to suppress Avalonia XAML compile warnings by adding the warning codes to the standard MSBuild
NoWarnproperty.Breaking changes
None
Obsoletions / Deprecations
None
Fixed issues
Fixes #11312