Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
1.0.0 nuget issue "Unable to resolve dependency 'Baseline'.
See original GitHub issueInstalling 1.0.0 from nuget on a fresh .net 4.6 solution, and i see this error.
Unable to resolve dependency 'Baseline'. Source(s) used: 'nuget.org', 'Microsoft Visual Studio Offline
I know there are other similar issues that were closed recently but this seems to be new/current.
Issue Analytics
- State:
- Created 7 years ago
- Comments:26 (18 by maintainers)
Top Results From Across the Web
NuGet Error NU1100
Issue. A dependency could not be resolved. This is a generic issue for types that are not packages or projects. Solution 1.
Read more >NuGet Package Dependency Resolution
This error occurs when one or more of the packages referenced in your project do not indicate that they support the project's target...
Read more >Unable to resolve Dependency in Installing a Nuget Package
The actual issue here is like one of my dependencies in my package is showing this error. The package is built-in Net Standard...
Read more >Some packages with only pre-release versions can not be ...
Install-Package : Unable to resolve dependency 'Foo (≥ 1.0.0-pre)'. At line:1 char:1 + Install-Package Bar -Version 1.0.0-alpha -Source .
Read more >Unable to Resolve dependencies after upgrade with NuGet
This article describes issues with resolving dependencies after upgrading with NuGet packages.
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
I don’t have anything helpful to contribute but just wanted to chime in that I’ve been experiencing these Baseline nuget issues for a long time as well. I guess I’m glad I’m not the only one.
FWIW, I don’t care what build system is used as long as I can forget about it and just get my work done.
@wastaz Why would dropping an external dependency be a breaking change, unless it has been used in such a way that users of Marten’s public API has been forced to use pieces from it in their code base? But if it could be made internal to Marten like expressed above, I guess it hasn’t. The people who has started to use Baseline as an effect of Marten can still have it as an external dependency. Agree that if the issue is in NuGet, then it would be great if it was fixed there. But if something can be done from project perspective other than stating something in the lines of “use Paket” that would in my mind be a nice gesture to people invested in NuGet, but of course, if it causes actual breaking changes, it should be planned.