Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Microsoft.AspNetCore.Mvc.NewtonsoftJson: package update info wrong for .NET Core 3.1

See original GitHub issue

Hi there,

I have a C# solution which uses the Microsoft.AspNetCore.Mvc.NewtonsoftJson package. Unfortunately since the release of .NET 5, both Rider and Visual Studio try to update it in my .NET Core 3.1 projects to v5.0.1 which fails.

The root problem can reproduced by running the command dotnet list package --outdated and observing the output:

Project `X` has the following updates to its packages
   [netcoreapp3.1]: 
   Top-level Package                              Requested   Resolved   Latest
   > Microsoft.AspNetCore.Mvc.NewtonsoftJson      3.1.10      3.1.10     5.0.1

I guess some meta-data need fixing somewhere?

BR, Mark

Issue Analytics

State:
Created 3 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

markm77commented, Dec 26, 2020

But we don’t want it to support multiple frameworks. We want it to support 5.0 only, which is what it currently does. I’m not sure why that shows as an updated to an app targeting 3.1.

That’s what I thought. And I can confirm if the update is attempted it fails on a .NET 3.1 project.

The problem is NuGet keeps suggesting the incorrect update. It does so in Rider, Visual Studio and on the command line. And then when you attempt the update it fails.

0reactions

Pilchiecommented, Dec 30, 2020

This issue was moved to NuGet/Home#10419