-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NuGet restore fails when encountering netcoreapp2.0 -> netstandard2.0 references #5065
Comments
I am having the same issue. Using this workaround allowed to build on hosted agent |
If you need a more recent version of NuGet you need to specify that in your definition. Due to a wide variety of compatibility issues in NuGet.exe we can't blindly update everyone to more recent versions |
Thank you @chrisrpatterson, I just found a vsts task to update a nuget. Is there an option to always use the most recent one? |
If you're using the NuGet Tool Installer task, you can use wildcards (e.g. 4.* or *) to always use the latest version available from https://dist.nuget.org. Note that things sometimes break or change between (even minor) versions, so this can introduce some instability to your build. |
Thanks @alexmullans, 4.3.0 works for us now |
It appears that the NuGet restore task in VSTS uses some old version of NuGet that is unable to deal with netcoreapp2.0 projects that reference netstandard2.0 projects.
This is running on a custom agent with VS 2017 update 3 and .NET Core SDK 2.0.0.
Directly invoking
nuget.exe restore
with NuGet 4.3.0 instead of using the NuGet task works fine. I would expect the NuGet task to also work fine here.Task log attached: 4_NuGet restore.txt
The text was updated successfully, but these errors were encountered: