NuGet restore fails when encountering netcoreapp2.0 -> netstandard2.0 references
See original GitHub issueIt 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
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Team Build Nuget restore failure with .NET Core 2.0 + . ...
I have a VS2017 solution that contains a .NET Core 2.0 console project that references a .NET Standard 2.0 class library, as well...
Read more >Troubleshooting NuGet Package Restore in Visual Studio
This error occurs when you attempt to build a project that contains references to one or more NuGet packages, but those packages are...
Read more >error netsdk1005 - You.com | The AI Search Engine ...
NuGet Manager version is 6.2.0. error NETSDK1005: Assets file doesn't have a target for 'netcoreapp3.1'. Ensure that restore has run and that you...
Read more >Deep-dive into .NET Core primitives: deps.json ...
Without a runtimeconfig.json file, this will fail with. > dotnet Program.dll A fatal error was encountered. The library 'libhostpolicy.dylib' ...
Read more >Even the simplest .NET Core project fails to build under ...
Obviously I'm referencing xUnit (2.2.0) via NuGet. This builds in VS (can't run it because it's a class library). However in NCrunch I...
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 Free
Top 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
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.
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