nuget pack csproj ('new style') does not include dependencies in resulting .nuspec

[gparlakov]

When packaging a csproj (the 'new' type generated by vs 2017 or dotnet cli - i.e. dotnet new classlib) the nuget packages dependencies included in the csproj do not get included in resulting nuspec file inside the generated package
Using dotnet pack works as expected. Also does Visual Studio build package option. I.e. these both generate the correct nuspec with dependencies.

Details about Problem

NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe):
NuGet Version: 4.7.1.5393

dotnet.exe --version: 2.1.402

VS version (if appropriate):15.8.4

OS version: windows 7 version 6.1 build7601: Service Pack 1

Worked before? If so, with which NuGet version:
Not sure.

Detailed repro steps so we can see the same problem (windows style path used below)

1. git clone https://github.com/gparlakov/nugetBug_depsDontGetIncluded

2. nuget restore .\nugetBug_depsDontGetIncluded\nugetBug.lib\nugetBug.lib.csproj

3. nuget pack nugetBug_depsDontGetIncluded\nugetBug.lib\nugetBug.lib.csproj -Build -outputDirectory ./output

4. Read the nuget.lib.nuspec from output\nuget.lib.1.0.0.nupkg- the deps included in nuget.lib.csproj are missing
   

Sample Project

https://github.com/gparlakov/nugetBug_depsDontGetIncluded

[dimmy-timmy]

Same behavior for me.
NuGet Version: 4.8.1.5435

dotnet pack works as expected

[npickett]

It appears from this post that nuget.exe pack currently doesn't support package reference based projects.

See #5979

[nkolev92]

Duplicate of #4491.

Please follow that issue for further updates.

[edufur]

It's funny. This problem keeps getting closed as "duplicate" and referenced to others that are actually DIFFERENT. This problem seems to be getting ignored.

[nkolev92]

@edufur
The answer here is use dotnet.exe/targets packing to pack SDK based projects.

[Rzpeg]

@nkolev92 targets packing with msbuild incorrectly packs the versions for referenced projects.
#5979 (comment)