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

Make .NET 4.7.2 and later support .NET Standard 2.0 (not 4.6.1+) #8376

Open
gravidThoughts opened this issue Jul 24, 2019 · 1 comment

Comments

@gravidThoughts
Copy link

commented Jul 24, 2019

Can I configure Nuget client infrastructure to behave like the default Paket configuration?

Per a fantastic article by Rick Strahl:

As a side note a number of people pointed out to me that Paket - which is an alternate package manager for NuGet packages - considers versions of .NET 4.7.1 and older incompatible with .NET Standard so you can't actually install .NET Standard packages for those versions by default.

Makes sense - Microsoft has acknowledged that using .NET Standard on anything prior to 4.7.1 is not a good idea and I would add using 4.7.1 is not optimal either, but alas it does work with some of the messy hackery described above.

At the end of the day though it's highly recommended that you don't use .NET Standard with 4.7.1 or earlier. Use 4.7.2 if you want to use .NET Standard.

@heng-liu heng-liu assigned heng-liu and rrelyea and unassigned rrelyea and heng-liu Jul 24, 2019

@rrelyea rrelyea changed the title Configure Nuget to behave like Paket in regards to .NET Standard 2.0 Make .NET 4.7.2 and later support .NET Standard 2.0 (not 4.6.1+) Jul 25, 2019

@rrelyea

This comment has been minimized.

Copy link
Contributor

commented Jul 25, 2019

@terrajobst, @anangaur - is this a good idea. how important?
yes, mistakes were made in this area...

if so, many ways we could enable.
0) keep same behavior

  1. change the default
  2. change the default, allow override to have old behavior
  3. keep same behavior, allow override to have 4.7.2 and above be NS2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.