Detected package downgrade warning (dotnet core, vs 2017)

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.

---

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.

---

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>

---

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!

---

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.

---

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.

---

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>

---

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.

---

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)

---

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

https://i.stack.imgur.com/zNq7c.png

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)

---

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

---

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.

---

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.

---

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.

---

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.

---

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.

---

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.

---

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>

---

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

---

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>

---