dotnet pack doesn't honor AppendTargetFrameworkToOutputPath in package structure

[emgarten]

From @thomaslevesque on November 8, 2017 11:44

This project used to produce the following package structure with the 1.0.4 SDK:

But with the 2.0.2 SDK, it produces this instead:

It looks like the AppendTargetFrameworkToOutputPath property is ignored by dotnet pack.

Is this change intentional? Is there a workaround?

Copied from original issue: dotnet/sdk#1717

[emgarten]

From @thomaslevesque on November 8, 2017 14:4

Apparently, including the TFM in the path is hard-coded and can't be disabled...

For the project I mentioned, it generates an analyzer packages that installs correctly in SDK-style projects, but not in classic csproj (the analyzer is not referenced).

[emgarten]

From @livarcocc on November 9, 2017 3:6

@emgarten Is this something that NuGet relies on the SDK for or is NuGet doing its own path calculation for the folder under pack?

[emgarten]

I'm not completely sure if NuGet appends the TFM to $(BuildOutputTargetFolder) here, or how this is getting added.

//cc @rohit21agrawal for pack

[emgarten]

From @thomaslevesque on November 10, 2017 16:18

I'm not completely sure if NuGet appends the TFM to $(BuildOutputTargetFolder) here, or how this is getting added.

From the code I linked to, it seems pretty clear that it does ;)

[emgarten]

From @livarcocc on November 10, 2017 16:50

I agree with @thomaslevesque. It seems NuGet is the one that is doing this and not honoring the Append property.

[emgarten]

From @blairconrad on November 14, 2017 2:38

It seems NuGet is the one that is doing this and not honoring the Append property.

Does this mean that the issue should move to NuGet/NuGet.Client?

[rohit21agrawal]

i disagree that pack should honor this property. This will lead to cases where DLLs are put right under lib folder and we don't want to encourage such packages.

Pack can only honor a property like this when restore knows how to make sense of these files without them being in the TFM folder - in those cases, users can manually set package paths.