dotnet pack doesn't honor AppendTargetFrameworkToOutputPath in package structure
See original GitHub issueThis 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?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
dotnet pack doesn't honor ...
It looks like the AppendTargetFrameworkToOutputPath property is ignored by dotnet pack . Is this change intentional? Is there a workaround?
Read more >asp.net - DotNet Pack Not Doing Anything
I am trying to create a nuget package for my web application but it is not producing any .nupkg outputs. I am using...
Read more >dotnet pack command - .NET CLI
The dotnet pack command builds the project and creates NuGet packages. The result of this command is a NuGet package (that is, a...
Read more >release-notes
A dependency manager for .NET with support for NuGet packages and git repositories.
Read more >Building NuGet packages with Dotnet Core | by Xavier Penya
The package doesn't work if I have multiple projects. dotnet pack just packs a single project. It doesn't pack all of its project...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
From the code I linked to, it seems pretty clear that it does 😉
This issue was moved to NuGet/Home#6184