Re enable IL warnings - #7566
Merged
Merged
Conversation
zivkan
reviewed
Jul 15, 2026
jebriede
approved these changes
Jul 16, 2026
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.
Bug
Fixes: #7559 (comment)
Description
some of the recent RUC annotations across dotnet are finally flowing into NuGet and causing the IL warnings.
source of suppression PR: dotnet/dotnet#5791
the PR that had them suppressed was a relatively old PR so it probably did not have the some of the AOT work we have done on NuGet.Client and suppression probably made sense at that time.
This PR brings back the warnings so that we get build fails if any new AOT incompatible code is added and keeps our core libraries AOT compatible
PR Checklist