2

I have a project specific roslyn source generator. It is a project reference in a library (which is also a project reference) in my application.

<ProjectReference Include="$(RepoRoot)\MyGenerator\MyGenerator.csproj" OutputItemType="Analyzer" ReferenceOutputAssembly="false"/>

It builds fine, both via dotnet build at the command line and with MSBuild in my IDE.

But, if I run roslynator, it fails to compile, claiming my autogenerated properties do not exist. Is this an inherit problem with the one pass approach to roslyn analyzers / source generators? Or is it something wrong in my setup and fixable?

I'm running roslynator fix MY_APP_CSPROJ --verbosity diagnostic and getting the compiler failure, while dotnet build succeeds.

Not sure it matters, but the top level application (unfortunately) is still a framework 4.7 project. The source generator is net standard 2.0. I'm stuck in a legacy code base. Cannot confirm or deny if the behavior is different targeting a modern project.

Improve this question
Related questions
64
C# Source Generator - warning CS8032: An instance of analyzer cannot be created
30
What are the effects of the "EnforceExtendedAnalyzerRules" flag in the project file
14
Make diagnostic errors reported by a C# source generator appear in the Visual Studio editor
Load 4 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.