"dotnet nuget push -s c:/localdir" creates flat directory structure

[vivainio]

Details about Problem

dotnet.exe --version: 3.1.101

OS version:

win10 1803

Detailed repro steps so we can see the same problem

$ dotnet nuget push -s C:\localdir myapp.1.3.0.nupkg

Observe that c:/localdir now contains myapp.1.3.0.nupkg at top level instead of the "new" hierarchical nuget directory structure.

[chausner-audeering]

I am using dotnet nuget push -s for copying a local package into the local cache and have noticed the following behaviour:

• If the local cache is non-empty and contains at least one other package already, NuGet correctly installs the package hierarchically.
• If the local cache is completely empty, the package is simply copied into it without the hierarchic structure. NuGet will also not find it when attempting to restore projects that reference the package.

This unexpected behavior makes it difficult to suggest dotnet nuget push -s as generic way to install packages to the local cache, because it only works if there are already other packages in the cache. It will not work for a clean installation.

[chausner-audeering]

Looking at the NuGet client source, my observations are confirmed. The client uses a heuristic to decide whether the offline feed is in v2 or v3 format. If the folder is completely empty, it defaults to v2 which means it will not create the hierarchic structure that NuGet expects for the cache folder.

[donnie-msft]

Duplicate issue: https://developercommunity.visualstudio.com/t/dotnet-nuget-push-cannot-create-a-hierar/10408599