Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Provide explicit ns2.0 binaries #357

Copy link
Copy link
@damageboy

Description

@damageboy
Issue body actions

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.

BlacKCaT27, samusaran, buvinghausen, PaitoAnderson and dan-butler-red-deer

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.