Determine why analyzers are running on generated not supported assemblies auto-generated files #84104
Labels
area-Infrastructure-libraries
tracking-external-issue
The issue is caused by external problem (e.g. OS) - nothing we can do to fix it directly
Milestone
Our root .editorconfig lists *.notsupported.cs as being consider auto-generated, but for some reason that .editorconfig isn't being passed to csc when building those assemblies, e.g. Microsoft.Win32.Registry. As a result, analyzers are running on the auto-generated .notsupported.cs file there.
The text was updated successfully, but these errors were encountered: