Allow MSBuildWarningsAsMessages with comma separation#11522
Merged
JaynieBai merged 5 commits intodotnet:mainfrom Mar 5, 2025
Merged
Allow MSBuildWarningsAsMessages with comma separation#11522JaynieBai merged 5 commits intodotnet:mainfrom
JaynieBai merged 5 commits intodotnet:mainfrom
Conversation
YuliiaKovalova
approved these changes
Mar 3, 2025
SimaTian
approved these changes
Mar 4, 2025
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.
Fixes #7094
Context
We don't support NAT011,NAT012, when warnings with comma separation, the Warings are not suppressed.
Changes Made
Parse warning codes with comma separation and semicolon
Testing
MSBuildWarningsAsMessagesWithCommaSeparation()
Notes