Detected package downgrade warning (dotnet core, vs 2017)

Question

I have just updated all my nuget packages for my solution (dotnet core 1.1 project).

I am now getting the following warnings and I don't really know what they mean.

Update: I am still getting warnings mentioned above. My web projects warn about the Microsoft.NETCore.App package (see screenshot below) and my lib projects warn about NETStandard.Library (see screenshot above)

When trying to update Microsoft.NETCore.App in the NuGet package manager, I am getting the following error:

Hope someone can help me get rid of those warnings and setup everything it is meant to be, so I can update all my packages.

Can you post the content of your .csproj file? – Drew Noakes Mar 17 '17 at 16:44 — Drew Noakes, Mar 17 '17 at 16:44

score 69 · Answer 1 · answered Sep 26 '17 at 16:23

69

This situation occurred to me after opening an existing solution but instead of Warnings, they were Errors.

I opened the YourAwesomeApp.csproj file and went through the "Detected package downgrade" errors one-by-one and manually changed the version of that line item from the existing version to the specified version that was shown in the error itself.

For example, if the Error says downgrade detected "SqlServer 1.0.4 -> 1.0.3" then find the line for package SqlServer and edit the version from 1.0.3 to 1.0.4.

Those errors should disappear after building the project.

The downside to this that I only had 5 errors this time but what if another person's project contained say 50 such errors. Then that person's task of manually editing those lines would be very tedious and time-consuming.

answered Sep 26 '17 at 16:23

Jimmy Shaw

1,097
1
12
19

7

This works for me when afterwards I did a `dotnet restore` on the failing to build project. – Aage Feb 14 '19 at 07:17
4

Worked for me but had to do a "Clean Solution" and then build. – Neville Oct 31 '19 at 09:50
1

Detected package downgrade: Microsoft.Extensions.Logging from 3.1.3 to 2.2.0. Reference the package directly from the project to select a different version. When I searched for Microsoft.Extensions.Logging I did not find any. – Gopi Apr 23 '20 at 12:38

score 62 · Answer 2 · answered Mar 08 '19 at 16:48

This generally happens because the item you are attempting to install requires a more recent version of a sub-dependency than you have already included in your project.

The solution is to update or delete the existing dependency that is in your project prior to installing the package.

Example:

Detected package downgrade: Newtonsoft.Json from 9.0.0 to 8.0.0.

This means you have Newtonsoft.Json 8.0.0 already listed as a dependency in your project, but the package you are trying to install requires at least version 9.0.0 as a dependency.

This is because Visual studio won't automatically upgrade this dependency as you've specified an explicit version for your project. You can either upgrade the dependency in your project to the minimum required version or remove it from your project, and let the package you're installing handle it.

To resolve this, in our example above, this would mean finding 'Newtonsoft.Json 8.0.0' and upgrading it to version '9.0.0' or simply removing it from your project prior to installing your package.

score 27 · Accepted Answer · edited Apr 05 '18 at 00:49

27

As per answer above the working solution is to remove the following line from your csproj file.

Web App project:

<RuntimeFrameworkVersion>1.0.4</RuntimeFrameworkVersion>

Lib project:

<NetStandardImplicitPackageVersion>1.6.0</NetStandardImplicitPackageVersion>

edited Apr 05 '18 at 00:49

johnnyRose

7,310
17
40
61

answered May 16 '17 at 05:01

Nik

2,863
6
24
29

Gerard Wilkinson · Answer 4 · 2017-09-21T16:01:07.583

20

In my case neither of those properties were set in my csproj files.

I had to tell VS to update those packages via NuGet.

The warnings appeared for me after resolving the warning for explicit reference to implicit dependency .NETCore.App after moving from 1.0 to 1.1.

UPDATE 21/09/17

This also seems to affect upgrades to 2.0, the resolution is the same. Update those packages manually with NuGet. Thanks to IbrarMumtaz for pointing this out!

edited Sep 21 '17 at 16:01

answered May 25 '17 at 13:43

Gerard Wilkinson

1,512
14
33

This is happening to me now from 1.1 > 2.0. : ? – IbrarMumtaz Sep 18 '17 at 15:31
It is almost definitely best to explicitly set your package versions rather than ignore the warning or try some other more generic solution. If you want to avoid the downgrades, be explicit about it. This is the best answer. – Dan Field Apr 23 '18 at 18:44
8

Unless nuget won't let you! Nightmare. – Oliver May 22 '18 at 16:18

score 19 · Answer 5 · edited Apr 10 '18 at 04:49

19

I was able to fix some error like that adding NoWarn in cproj

<Project Sdk="Microsoft.NET.Sdk">

 <PropertyGroup>
    <NoWarn>$(NoWarn);NU1605</NoWarn>
  </PropertyGroup>

...
</Project>

You may want to add it only temporarily during multiple package upgrade and remove it later.

edited Apr 10 '18 at 04:49

Michael Freidgeim

26,542
16
152
170

answered Oct 18 '17 at 17:02

mrapi

5,831
8
37
57

4

The only problem is that "temporarily" inevitably becomes permanently. Either whoever makes the change forgets to change it back or doesn't document it and maintenance gets passed to someone else who never knew about the temporary fix in the first place. Or they never have time to deal with it and it eventually fades into the mists of time, unchanged. – Simon Elms Sep 24 '21 at 04:39

score 12 · Answer 6 · answered Mar 17 '17 at 19:39

I was able to get rid of these warnings in my project by removing the <NetStandardImplicitPackageVersion> element from the csproj file.

There's some information in this article about implicit metapackages, which seems to be the root cause of this problem.

You might also need to update some dependencies. For example, I had to upgrade BenchmarkDotNet from 0.10.1 to 0.10.3 to get rid of a few warnings like the ones you're seeing.

Emil · Answer 7 · 2018-07-18T17:15:19.103

8

Try removing:

<IsPackable>false</IsPackable>

from your project file - this is what worked for me!

If you are still left with NU1605 Error code you can ignore it by adding the following to your project file:

<PropertyGroup>
    <NoWarn>NU1605</NoWarn>
</PropertyGroup>

edited Jul 18 '18 at 17:15

answered Jul 18 '18 at 17:06

Emil

2,196
2
25
24

I did the nowarn solution to be able to publish the latest 3.1.0-preview4.19579.2 to azure webapp. – Magnus Karlsson Dec 08 '19 at 21:58
yes this works, as long as you are OK with ignoring this particular warning in your build :) – Emil Dec 09 '19 at 18:20

score 5 · Answer 8 · edited Jan 30 '19 at 07:00

Try using NuGet

I was getting:

error NU1605: Detected package downgrade: System.Net.NameResolution from 4.3.0 to 4.0.0. Reference the packagedirectly from the project to select a different version.

So I referenced the package directory by running (in the project folder):

dotnet add package System.Net.NameResolution

See NuGet Errors - NU1605

Issue:

A dependency package specified a version constraint on a higher version of a package than restore ultimately resolved. That is, because of the "nearest wins" rule when resolving packages, a nearer package in the graph may have overridden a distant package.

Solution:

Add a direct reference to the project for the higher version of the package that you want to use.

score 5 · Answer 9 · answered Feb 18 '21 at 11:41

Identify the package detected. For example in my case, it is System.Diagonistics.DiagonsticSource
Find the location of this assembly reference from your project (Reference > Properties > Path)
Copy path and check. In my case, the project is referencing 4.6.0 but the assembly that I was about to install requires version 5.0.0 of System.Diagonistics.DiagonsticSource as minimum

Go to Manage NuGet Packages for the project and search for "System.Diagonistics.DiagonsticSource" and update. Bear in mind that this may also cause another "Detected package downgrade" error (you should go back to step one if this happens)
Now, install the assembly you initially wanted to install (In my case it was Microsoft.ApplicationInsights)

score 3 · Answer 10 · answered Nov 03 '18 at 11:29

In my case, this error was not related to .NET Core but to .NET Standard.

I had two libraries A, and B. Library A depended on some nuget package X, and library B depended on A. Once I upgraded X to a new version, somehow it started depending on a new version of NETStandard.Library nuget package (from 2.0.2 to 2.0.3), which broke the build of B with the error Detected package downgrade: NETStandard.Library from 2.0.3 to 2.0.2. Reference the package directly from the project to select a different version.

Once I added the NETStandard.Library nuget package as a dependency to B (obviously targetting the latest version 2.0.3), the error went away, even if a new warning appeared:

/usr/local/share/dotnet/sdk/2.1.403/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.DefaultItems.targets(5,5): Warning NETSDK1023: A PackageReference for 'NETStandard.Library' was included in your project. This package is implicitly referenced by the .NET SDK and you do not typically need to reference it from your project. For more information, see https://aka.ms/sdkimplicitrefs (NETSDK1023) (GWallet.Frontend.XF)

i updated project "B" as you explained, not worked for me. but thanks. this gives me some understanding to find other solution — Pajri Aprilio, Dec 20 '18 at 13:01
still not found yet. but i'm trying to remove dependency between A and B first, then make A and B dependent to the same version of X then add dependency between A and B again — Pajri Aprilio, Dec 20 '18 at 13:15

score 2 · Answer 11 · answered May 13 '18 at 11:06

2

Manually removing the nuget packages dependencies from the project and Install-Package for each of them fixed the problem in my case.

answered May 13 '18 at 11:06

Max Favilli

6,161
3
42
62

score 2 · Answer 12 · answered Jun 09 '20 at 10:58

2

The issue for me was that I had packages installed locally that were of higher versions than my projects referenced. If you go to Tools > NuGet Package Manager > Package Manager Settings > General > Clear All NuGet Cache(s) then rebuild your solution it'll install the packages referenced and the errors will go.

answered Jun 09 '20 at 10:58

Dystar

97
8

1

This is a very bad idea if you your package-feed/network is slow as it might take a very long time to load all your packages – Tharaka Aug 26 '20 at 05:58
2

I'm not sure why this would fix things. It will however take a while to retrieve all your packages against though. – Ben Power Nov 02 '20 at 22:36
I went from 3 to 24 errors... at least them all are different errors – Felipe Diniz Mar 08 '22 at 09:22

score 1 · Answer 13 · answered Jul 25 '18 at 16:35

1

I was trying to upgrade Microsoft.AspNetcore.MVC to Version 2+. The solution for me was to upgrade all of the other dependencies first to 2+, then finally upgrade .MVC.

answered Jul 25 '18 at 16:35

Eric

7,930
17
96
128

score 1 · Answer 14 · answered Aug 27 '18 at 11:04

1

I could solve the problem by downloading earlier version of the package causing the problem, that seems to be caused by depending on a .NET Standard version that's not installed, this also should be solved by updating Visual Studio.

answered Aug 27 '18 at 11:04

mshwf

7,009
12
59
133

score 1 · Answer 15 · answered Jan 22 '20 at 14:00

1

If you're getting this error for Razor in a netcoreapp3.1, you just need to change the project SDK from Microsoft.NET.Sdk.Razor to Microsoft.NET.Sdk.

answered Jan 22 '20 at 14:00

Boiethios

38,438
19
134
183

1

how to do it in rider ? – kuldeep Mar 16 '20 at 15:50
1

@kuldeep Open the `csproj` with F4 and replace the text – Boiethios Mar 16 '20 at 15:52

score 1 · Answer 16 · answered Jun 03 '20 at 11:55

1

so, try to uninstall the package entirely and install it again. make sure you do this for all the solution projects reference it. then just clean and rebuild. this worked for me.

answered Jun 03 '20 at 11:55

eva

89
1
2

score 1 · Answer 17 · edited Oct 06 '20 at 07:43

1

I had a similar issue, where my project had package reference like this:

Package references:

Package A
Package B
    Package A

So because project B reference package A, I just deleted package A from the main packages list and was left with Package B referencing Package A. I rebuilt the solution and the problem was gone.

edited Oct 06 '20 at 07:43

Dharman

30,962
25
85
135

answered Oct 06 '20 at 07:38

Yair A.

11
2

score 1 · Answer 18 · answered Oct 15 '20 at 09:31

For me it was caused by referencing a project using a specified version of Microsoft.AspNetCore.App where my project did not :

My project :

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.App"/>
  </ItemGroup>

referenced project :

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.2" />
  </ItemGroup>

Fix (My project) :

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.2" />
  </ItemGroup>

score 0 · Answer 19 · answered Sep 16 '22 at 15:51

0

For my project, clean and rebuild not solve my problem. After some search, I try to remove all the debug/obj folder, then rebuild and it works, wish this can help anyone who encounter this problem.

answered Sep 16 '22 at 15:51

SLdragon

1,477
16
19

score 0 · Answer 20 · answered Feb 07 '23 at 08:13

I got the problem while trying to add "Npgsql.EntityFrameworkCore.PostgreSQL.Design" into my ASP.NET Core 7 MVC project. Here is the error I had;

Error NU1605 Detected package downgrade: NETStandard.Library from 2.0.0-preview1-25301-01 to 1.6.1. Reference the package directly from the project to select a different version.

I fixed it by adding the following line into my .csproj file;

<PackageReference Include="NETStandard.Library" Version="2.0.0-preview1-25301-01" />

Note: no line was present for this package, I copied the name and the version from the error. afterwards, do a clean and build and the error should be gone and you should be able to add whatever package you were trying to add. if error still doesn't go away, try "dotnet restore" in package manager console window.

score -1 · Answer 21 · answered Jan 19 '18 at 00:38

-1

I just recently came across this issue and updating the NuGet packages was what worked for me.

answered Jan 19 '18 at 00:38

combatc2

1,215
10
10

1

what nuget packages exactly? this answer is very ambiguous – knocte Nov 03 '18 at 09:37

score -1 · Answer 22 · answered Oct 02 '18 at 14:03

-1

I solved this issue thanks to this answer. Basically, just add the following line inside the <PropertyGroup> tags in your .csproj file:

<TargetLatestRuntimePatch>true</TargetLatestRuntimePatch>

answered Oct 02 '18 at 14:03

Shaul Behr

36,951
69
249
387

Detected package downgrade warning (dotnet core, vs 2017)

22 Answers22

UPDATE 21/09/17

Try using NuGet

Linked