You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a framework dll has a NuGet package and is referenced with both Package- and FrameworkReference the dll from the package will be copied to the output.
Steps to reproduce
I have prepared a sample repository. The build output for WebApplication.PackageReferenceDependency contains the Microsoft.AspNetCore.Http.Connections.Common.dll and others, wich should be resolved with the Microsoft.AspNetCore.App FrameworkReference and therefore should not be copied to the output.
We may close this issue if:
The references (*.deps.json) do not contain framework dlls with the versions from NuGet
The NuGet versions of framework dlls are no longer copied to the build output
Results of first analysis
The PackageReferenceDependency task seems to decide, that the NuGet dlls need to be copied to the output.
This is partially caused by the NuGet package for Microsoft.AspNetCore.Http.Connections.Client. There is already an issue to change the package generation, but the sdk should still be changed to resolve such conflicts.
Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue!
If you believe this issue was closed out of error, please comment to let us know.
Description
When a framework dll has a NuGet package and is referenced with both Package- and FrameworkReference the dll from the package will be copied to the output.
Steps to reproduce
I have prepared a sample repository. The build output for WebApplication.PackageReferenceDependency contains the Microsoft.AspNetCore.Http.Connections.Common.dll and others, wich should be resolved with the Microsoft.AspNetCore.App FrameworkReference and therefore should not be copied to the output.
We may close this issue if:
Results of first analysis
Possibly related issues
Further technical details
dotnet --info
:The text was updated successfully, but these errors were encountered: