build: enable all .NET analyzers in every build (AnalysisMode=All) - #166
Merged
Conversation
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
…=All Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
DeepDiver1975
force-pushed
the
build/analyzer-all-mode
branch
from
August 31, 2026 07:29
e1eb593 to
ffff02a
Compare
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
1 participant
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.
Summary
Final step of the analyzer-hardening series: flips
AnalysisMode=Allon inDirectory.Build.props, so every build (Debug and Release, all projects) runs every .NET analyzer at default severity withTreatWarningsAsErrors— identical conditions to the long-lived verification harness. After the preceding eleven PRs, the repo is warning-free under these settings, so CI stays green.Previously analyzers only ran under
AnalysisMode=Allwhen explicitly enabled, so regressions would slip past CI; now they fail the build instead.Verification
dotnet build(Debug and Release, no flag overrides): 0 warnings, 0 errors.