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 packing a tool that uses NuGet aliases, the nupkg itself should put its output files under the concrete framework shortname, rather than the alias. This was fixed in other NuGet packaging scenarios for NuGet/Home#10020, but packing tool projects is still affected, and I'm told this is not under NuGet's control, so I'm filing a bug here.
When packing a tool that uses NuGet aliases, the nupkg itself should put its output files under the concrete framework shortname, rather than the alias. This was fixed in other NuGet packaging scenarios for NuGet/Home#10020, but packing tool projects is still affected, and I'm told this is not under NuGet's control, so I'm filing a bug here.
Repro
dotnet new console -n baz
cd baz
dotnet pack
nupkg
dirtools
directorycsproj
Expected
tools/net5.0-windows7.0/any/...
Actual
tools/net50-windows/any/...
Sample project
You can just extract this one and run
dotnet pack
on it.baz.zip
The text was updated successfully, but these errors were encountered: