You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…alyzers to be analyzed
Fixesdotnet/vscode-csharp#6057
We were not accounting for the fact that changing the background analysis scope option can increase the set of analyzers to analyze (when option value is changed from None to OpenFiles or FullSolution). Hence we ended up using a cached CompilationWithAnalyzers instance which only had compiler analyzer instance, causing the given ArgumentException.
mavasani
added a commit
to mavasani/roslyn
that referenced
this issue
Aug 7, 2023
…alyzers to be analyzed
Fixesdotnet/vscode-csharp#6057
We were not accounting for the fact that changing the background analysis scope option can increase the set of analyzers to analyze (when option value is changed from None to OpenFiles or FullSolution). Hence we ended up using a cached CompilationWithAnalyzers instance which only had compiler analyzer instance, causing the given ArgumentException.
I am intermittently seeing the below exception in C# extension when changing background analysis scope option for compiler and analyzer diagnostics:
I believe there seems to be a missing check for empty trimmed down analyzers based on these options.
The text was updated successfully, but these errors were encountered: