-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Pack command generates incorrect dependencies #484
Comments
Looks like a bug. Pack should create a group for each TFM in the project for each asset type (ex: lib, build, dependencies) to avoid falling back to the wrong group like you are seeing here. |
It happened when there should have been an empty dependency group. When I added a "global" |
Moved to NuGet/Home#4137 |
mmitche
pushed a commit
to mmitche/sdk
that referenced
this issue
Jun 5, 2020
…213.1 (dotnet#484) This change updates the following dependencies - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19113.1
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I have a project which cross compiles to many target frameworks, including desktop .NET 4.5.
I have the
NETStandard.Library
excluded fromnet45
as many users complain when adding that dependency. When I then runmsbuild /t:pack
ordotnet pack
(same thing), the dependencies it generates includesnetstandard1.0
(which is a valid target platform), but it does not generate an empty group fornet45
. It's not properly calculating the dependencies that only affectnet45
.The result is that the
net45
package will resolve and get thenetstandard1.0
set of dependencies because there's no explicitnet45
dependency group and that's the problem.Here's what it generates:
And here's the csproj that created it.
The text was updated successfully, but these errors were encountered: