Expose CompilerVisibleProperty to AnalyzerConfigOptionsProvider.GlobalOptions #301
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.
When creating a
.csproj
file:The value of the
<CustomProperty>
is exposed to theAnalyzerConfigOptionsProvider.GlobalOptions
within the context of a Roslyn code analyzer. How Roslyn solves this is as follows:It generates an
.editorcofig
file with the name:obj/{Configuratioin}/{TargetFrameWork}/{ProjectFileName}.GeneratedMSBuildEditorConfig.editorconfig
.In the reproducer this is the body:
To actually solve this, this file has to be added to the
AnalyzerConfig
somehow. I'm not sure if this can be achieved in Buildalyzer, or that it is only possible to do this when spinning up the diagnostics.