Skip to content

[CLI] Make analyzer type loading resilient and log System.Composition redirects - #1842

Merged
josefpihrt merged 2 commits into
mainfrom
fix/analyzer-assembly-load-resilience
Oct 4, 2026
Merged

josefpihrt merged 2 commits into
mainfrom
fix/analyzer-assembly-load-resilience

Conversation

@josefpihrt

Copy link
Copy Markdown
Collaborator

Follow-up to #1831.

  • Skip analyzer and code fix provider types whose attributes cannot be read or whose instance cannot be created (FileNotFoundException, FileLoadException, BadImageFormatException, TypeLoadException) instead of aborting the whole run. Details are logged at diagnostic verbosity.
  • Log each System.Composition redirect at diagnostic verbosity.
  • Rename AnalyzerDependencyResolver to CompositionAssemblyResolver (avoids confusion with AnalyzerAssemblyLoader), remove the _isRegistered guard, use a collection expression.

No changelog entry.

Made with Cursor

Josef Pihrt and others added 2 commits October 4, 2026 14:32
… redirects

- Skip analyzer and code fix provider types whose attributes or instance
  cannot be loaded instead of aborting the whole run.
- Log each System.Composition redirect at diagnostic verbosity.
- Rename AnalyzerDependencyResolver to CompositionAssemblyResolver, drop the
  _isRegistered guard and use a collection expression.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@josefpihrt
josefpihrt merged commit eb949f0 into main Oct 4, 2026
17 checks passed
@josefpihrt
josefpihrt deleted the fix/analyzer-assembly-load-resilience branch October 4, 2026 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant