paket pack with multi-targeted project only creates first framework specified

[ozwaldDunlop]

Description

using paket pack on a project with multiple TargetFrameworks creates a nupkg with only the first specified framework. ie. if the declaration is <TargetFrameworks>netstandard2.0;net472</TargetFrameworks>, then the nupkg has just the netstandard2.0 contents.
If they're swapped round:
<TargetFrameworks>net472;netstandard2.0</TargetFrameworks>, then the nupkg has just the net472 contents.

Repro steps

Get this repo: https://github.com/ozwaldDunlop/paket-multitarget-bug

1. Run .paket\paket.exe install
2. Build in Debug mode
3. Run .paket\paket.exe pack . --build-config Debug
4. Open the resulting nupkg in 7zip or Nuget Package Explorer

Expected behavior

You should see netstandard2.0 and net472 folders in the nupkg as you do when you run dotnet pack:

Actual behavior

You only see one lib folder:

Known workarounds

Use dotnet pack instead of paket pack

[generik0]

I am also interested in this, very much.
dotnet pack is not working for me. dotnet pack is doing something very weird and generating a long path for the nuspec it created. NuGet/Home#3324

[fjoppe]

Swapping the frameworks around gives the above behavior, even without rebuild.

I've even tried to "paket pack" the stuff in the netstandard2.0 folder, it even then came with a net45 folder in the nupkg.

[forki]

Did you try dotnet pack? Paket integrates into that and it allows multi targeting Am Sa., 2. Feb. 2019, 21:42 hat Frank Joppe <[email protected]> geschrieben:

…

Swapping the frameworks around gives the above behavior, even without rebuild. I've even tried to "paket pack" the stuff *in* the netstandard2.0 folder, it even then came with a net45 folder in the nupkg. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3494 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgND8nzMmbBp_11NyP1hurMbwBhW9vks5vJfgvgaJpZM4aV1yb> .

[fjoppe]

Yes, I was experimenting with that. The result appeared good. However, my question (for me) is, what is the best choice now, to put in my FAKE5 build script? Dotnet pack or paket pack? I don't know at this point. I o like the Paket integration in FAKE.

[forki]

Dotnet pack is probably the way to go forward. Am So., 3. Feb. 2019, 08:57 hat Frank Joppe <[email protected]> geschrieben:

…

Yes, I was experimenting with that. The result appeared good. However, my question (for me) is, what is the best choice now, to put in my FAKE5 build script? Dotnet pack or paket pack? I don't know at this point. I o like the Paket integration in FAKE. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3494 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNDTQf62-yvbO_HoYReIvYpsVrrF8ks5vJpZngaJpZM4aV1yb> .

[jam40jeff]

@forki The problem is that dotnet pack doesn't support many of the settings that paket pack does. Namely, I need --interproject-references fix.

I think we need to make paket pack work. It is still a valid replacement for dotnet pack just as it was for nuget pack.

[jam40jeff]

@forki I believe PR #3534 should be ready to go and will fix this.