Skip to content
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

Provide explicit ns2.0 binaries #357

Closed
damageboy opened this issue Dec 17, 2017 · 2 comments
Closed

Provide explicit ns2.0 binaries #357

damageboy opened this issue Dec 17, 2017 · 2 comments

Comments

@damageboy
Copy link

I understand this might sound like an odd request to say the least, but I'm encountering an extremely annoying issue when trying to restore my own project(s) which are dependent on both external ns1.x and ns2.0 nuget packages... (for example dapper + ssh.net).

Here are a couple of previous issues reporting similar errors with other nugets:
dotnet/core#907
dotnet/sdk#1792

Here's a sample repro repo from the last issue:
https://github.com/ogreenz/rid-netstandard2-repro

Basically, the gist of this is that nugets that require a ns1.x dependency while a ns2.0 dependency is also required are "forcing" a downgrade of the stdlib nugets like for example System.IO.FileSystem.Primitives

The only solution I could find is to forcefully request a version >= 4.3.0 in my OWN project or face the cryptic NU1605 warning which is treated by default as an error since sometime during the netcore 2.0.0 preview period...

It would be great if users are not forced to individually deal with this cryptic error by providing a ns2.0 binary as part of the official nugets.

@drieseng
Copy link
Member

Pfew, time flies :(
This landed long time ago on the develop branch, but until now I haven't gotten around to pushing a new release.
I'm trying to pick up speed again (and putting other OSS work on hold).

@drieseng drieseng added this to the 2020.0.0-beta1 milestone Jan 22, 2020
@drieseng
Copy link
Member

This will be part of the upcoming beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants