dotnet pack doesn't honor AppendTargetFrameworkToOutputPath in package structure

[thomaslevesque]

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?

[thomaslevesque]

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).

[livarcocc]

@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

[thomaslevesque]

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 ;)

[livarcocc]

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

[blairconrad]

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?

[emgarten]

This issue was moved to NuGet/Home#6184