Pack library with analyzer

It is common to have:

Lib.csproj
Lib.Analyzers.csproj

Where Lib.csproj does not have a project reference to Lib.Analyzers.csproj but we want Lib.nupkg to have package dependency to Lib.Analyzers.nupkg

When using paket for packing it is just a matter of adding the following to paket.template:

dependencies
  Lib.Analyzers

I tried adding a fake project reference as a hack

  <ItemGroup>
    <ProjectReference Include="..\Lib.Analyzers\Lib.Analyzers.csproj">
      <!-- hack for packing with package dependency -->
      <PrivateAssets>none</PrivateAssets>
      <ReferenceOutputAssembly>false</ReferenceOutputAssembly>
      <SkipGetTargetFrameworkProperties>true</SkipGetTargetFrameworkProperties>
      <UndefineProperties>TargetFramework</UndefineProperties>
    </ProjectReference>
  </ItemGroup>

But it did not work and had issues when building.

Is there support for this scenario and if so where is it documented?

[jnm2]

What happens if you add SkipGetTargetFrameworkProperties="True" to the project reference? (https://gist.github.com/rainersigwald/1fbd21a24a41b9b7c6204cb9cfcbb1cf#disabling-targetframework-negotiation)

[ericstj]

I think nuget/home might be a better repository. NuGet owns the Pack task and pack gets all its information about dependencies from the csproj (actually assets file, I believe).

any magic metadata that would allow us to work around this?

One thing you might want to try: https://docs.microsoft.com/en-us/visualstudio/msbuild/common-msbuild-project-items?view=vs-2019#projectreference

<ProjectReference Include="..\Lib.Analyzers\Lib.Analyzers.csproj" ReferenceOutputAssembly="False" />