"Ambiguous invocations", "duplicate attribute", "Member with the same signature is already declared"

Hi,

We are using GraphQl server side, and we use the package HotChocolate for this.

For the client, we generate a client library.

For this, I have a .Net core class library that generates the code (using StrawberryShake packages)

<PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <ImplicitUsings>enable</ImplicitUsings>
        <Nullable>enable</Nullable>
</PropertyGroup>
<ItemGroup>
        <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="6.0.0" />
        <PackageReference Include="Microsoft.Extensions.Http" Version="6.0.0" />
        <PackageReference Include="StrawberryShake.CodeGeneration.CSharp" Version="12.11.0" />
        <PackageReference Include="StrawberryShake.CodeGeneration.CSharp.Analyzers" Version="12.11.0" />
        <PackageReference Include="StrawberryShake.Transport.Http" Version="12.11.0" />
        <PackageReference Include="StrawberryShake.Transport.WebSockets" Version="12.11.0" />
</ItemGroup>

In our console client, using that library, we configure the ServiceCollection, using the generated methods.

But when opening that generated code, Resharper complains a lot. (700 errors or so in total)

While dotnet simply compiles and runs the code correctly.

I checked the duplicate attribute in the generated code - it is not there.

I checked the ambiguous reference in the generated code - there is only one package that has that code - correct, no problem.

All the other stuff is also correct - compiles, and runs fine.

But Resharper sees a lot of problems.

So I wanted to create an issue in YouTrack, reproducing this situation.  Turns out resharper does not complain in the custom solution, while it has the same generated projects ?!

So it seems solution related, right ?

Then I went back to the original solution and cleared the cache of Resharper - still same problems.

Any ideas from the community ?