Unity Issue Tracker - Failure to skip analysis of code generated by MonoScriptInfoGenerator when the Roslyn analyzer that inherits from DiagnosticAnalyzer is used
Fixed
UUM-72953
Failure to skip analysis of code generated by MonoScriptInfoGenerator when the Roslyn analyzer that inherits from DiagnosticAnalyzer is used
How to reproduce:
1. Open the “AnalyzerUnityTest“ project
2. Open the “SampleScene“
3. Enter the Play Mode
4. Exit the Play Mode
5. Navigate to the projects folder
6. Observe the “VisitedFiles.txt“ file
Expected result: No “Unity.MonoScriptGenerator.MonoScriptInfoGenerator“ files are checked by the analyzer
Actual result: “Unity.MonoScriptGenerator.MonoScriptInfoGenerator“ files are checked by the analyzer
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: Windows 10 Pro (22H2)
Note: The issue is caused when the code snippet “context.ConfigureGeneratedCodeAnalysis(GeneratedCodeAnalysisFlags.None)“ is placed in the Initialize method of the Roslyn analyzer script
Prioritise and Follow this issue
Have a workaround or additional info about this issue?