Fix TypeInitializationException during solution rebuilds with lazy initialization #8
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.
Solution rebuilds were failing with
System.TypeInitializationExceptionerrors for all analyzer classes as shown in the error screenshot. The issue occurred because static readonlyDiagnosticDescriptorfields were immediately accessingResourcesduring type initialization, but the embedded resource file wasn't always available when MSBuild/Roslyn loaded the analyzer types during rebuild scenarios.Root Cause
The analyzers used static readonly fields that eagerly accessed resources:
During rebuilds, this caused type initialization failures when the resource wasn't yet available.
Solution
Replaced eager static initialization with lazy initialization using
Lazy<T>:This defers resource access until the rule is actually needed, preventing initialization exceptions during rebuilds while maintaining full API compatibility.
Changes Made
BracesForControlFlowAnalyzerwith lazy initializationEnumAssignmentAnalyzerwith lazy initializationObjectInitializationAnalyzerwith lazy initializationTesting
Fixes #7.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.