Reference to "Microsoft.NETFramework.ReferenceAssemblies.net40" bubbling up

Hi there,

VS shows “Microsoft.NETFramework.ReferenceAssemblies.net40” being added to a net462 project with the latest release:

Reason is that the package reference is not defined as private:

    <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies.net40" Version="1.0.2" />

nuget.org provides following snippet (also for 1.0.2):

<PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies.net40" Version="1.0.3">
  <PrivateAssets>all</PrivateAssets>
  <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>

Was the reference just manually added, or is there a reason behind making the dependency transient? If not, could you possible revert to a private one?

And, could you possibly update the reference to 1.0.3?

Best Andreas

[tom-englert]

Usually I prefer a flat history without the cluttered graph generated by merge, which is more confusing than helpful. (https://www.tugberkugurlu.com/archive/resistance-against-london-tube-map-commit-history-a-k-a--git-merge-hell)

Anyhow, thanks to dependabot the history of all Fody repos is rendered totally useless, so using merge instead of rebase would not make it worse.

[tom-englert]

I have one machine where it doesn’t work without, but only within VS, MSBuild works fine. Got no clue where the root cause is.

Also having net40 as the first entry in the <TargetFrameworkds> results in this fancy behavior, where VS is playing with itself: (I don’t click anything, and this will run forever)