Upgraded .NET core version but VS 2019 needs to downgrade references

Question

0.00/5 (No votes)

See more:

I have a solution in VS2019 that I upgrade the .NET Core version from 1.1 to 2.1
However, I got a bunch of errors that I need to downgrade versions of System.net.socket, primitives and diagnostic tools.

Here's one of the errors

Install-Package : NU1605: Detected package downgrade: System.Net.Primitives from 4.3.0 to 4.0.11. Reference the package directly from the project to select a different version. 
 'myproject' -> Microsoft.VisualStudio.Web.BrowserLink 1.1.3 -> Microsoft.Extensions.FileProviders.Physical 1.1.1 -> NETStandard.Library 1.6.1 -> System.Net.Primitives (>= 4.3.0) 
 myproject-> Microsoft.VisualStudio.Web.BrowserLink 1.1.3 -> System.Net.Primitives (>= 4.0.11)

What I have tried:

I tried running update-package -reinstall, but it says no upgrade is needed for the project.

It's weird because the only reference installed among the mentioned assemblies in the error is BrowserLink which is in version 1.1.3

Posted 5-Jul-21 23:32pm

Bob Jason Tiamsic

Updated 6-Jul-21 0:01am

v2

Add a Solution

Comments

[no name] 6-Jul-21 13:40pm

BrowserLink is at 2.2.0; you're referencing a 2017 version.

Bob Jason Tiamsic 7-Jul-21 10:03am

Added a PackageREference stated in here: https://docs.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1605

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Bob Jason Tiamsic · Answer 1 · 2021-07-07T04:00:00

Solution 1

I added this PackageReference

<PackageReference Include="Microsoft.NETCore.Targets" Version="3.0.0" PrivateAssets="all" />

NuGet Warning NU1605 | Microsoft Docs[^]

Posted 7-Jul-21 4:00am

Bob Jason Tiamsic

Updated 7-Jul-21 4:05am

Comments

OriginalGriff 7-Jul-21 10:06am

Please don't repost if your solution does not appear immediately: all of these went to moderation and required a human being to review them for publication. In order to prevent you being kicked off as a spammer, they all had to be accepted, and then I have to clean up the spares. Have a little patience, please!
I've deleted the other versions.

Bob Jason Tiamsic 7-Jul-21 11:00am

understood. Wasn't aware of that. Thank you!