Microsoft.AspNetCore.Mvc.NewtonsoftJson Net6.0 on Net5.0
See original GitHub issueDescription
Paket is not resolving Microsoft.AspNetCore.Mvc.NewtonsoftJson
according to the target framework. Its resolving to Net6.0 which is wrong.
error NU1202: Package Microsoft.AspNetCore.Mvc.NewtonsoftJson 6.0.0 is not compatible with net5.0 (.NETCoreApp,Version=v5.0). Package Microsoft.AspNetCore.Mvc.NewtonsoftJson 6.0.0 supports: net6.0 (.NETCoreApp,Version=v6.0)
Thanks
Issue Analytics
- State:
- Created 2 years ago
- Reactions:10
- Comments:8
Top Results From Across the Web
c# - Microsoft.AspNetCore.Mvc.NewtonsoftJson 6.0.2 is not ...
Microsoft.AspNetCore.Mvc.NewtonsoftJson is a library that integrates Newtonsoft.Json with ASP.NET Core MVC so that it uses Newtonsoft.
Read more >Microsoft.AspNetCore.Mvc.NewtonsoftJson 6.0.1
Version Downloads Last updated
8.0.0‑preview.7.23375.9 3,867 13 days ago
8.0.0‑preview.6.23329.11 4,596 a month ago
8.0.0‑preview.5.23302.2 3,346 2 months ago
Read more >Microsoft.AspNetCore.Mvc.NewtonsoftJson Namespace
Provides types required to support Newtonsoft.Json based formatters. Classes. JsonSerializerSettingsProvider. Helper class which provides Newtonsoft.Json.
Read more >MvcNewtonsoftJsonOptions Class
Configures the casing behavior of JSON serialization to use the member's casing for property names, properties of dynamic types, and dictionary keys. Applies...
Read more >NewtonsoftJsonMvcBuilderExten...
Configures Newtonsoft.Json specific features such as input and output formatters.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would also like to say this is occurring to our team as well. So, bump!
I’m having the same problem in one of my projects.
framework: auto-detect
is ignored, along withframework: 5.0
. I also have a problem in this project where every time I runpaket update
it adds<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
to my csproj file, even if I haveredirects: off
in mypaket.dependencies
. That makes me wonder if there’s a deeper problem that’s causing the “ignoring framework restrictions” behavior and other undesired behavior.I’ve tried cleaning, rebuilding, deleting
obj
andbin
folders, deleting and reinstalling paket. Nothing seems to work and it keeps installing framework 6 packages into the framework 5 project. The only thing that fixes is it restricting the package versions inpacket.dependencies
and it’s a massive rabbit hole with the Microsoft packages trying to do all the transitive dependencies.