dotnet-apiport
dotnet-apiport copied to clipboard
microsoft
considers Newtonsoft.Json to be available on Core, but not on Desktop.
I ran it on the desktop version of the dll in this package: https://www.nuget.org/packages/Microsoft.AspNet.WebApi.Client/5.2.3
It says it's 100% compatible with .NET Standard and .NET Core - which is great. But it says it's only 89.7% compatible with .NET Framework. Which makes no sense as it's a .NET Framework asset.
It looks like it considers Newtonsoft.Json to be available on Core, but not on Desktop.
I have the same problem.
I have Newtonsoft.Json 11.0.2 in my repo, used in a project that runs .NET Framework 4.6 in production. Newtonsoft.Json.JsonConvert, Newtonsoft.Json.Linq.JObject, and Newtonsoft.Json.JsonPropertyAttribute are getting incorrectly flagged as "Not Supported" in .NET Framework 4.6.
I ran this using the Visual Studio Extension.
@rabrahamOpti This is an a false negative. The issue is with the catalog. (see: https://apisof.net/catalog/Newtonsoft.Json)
It is not part of the .NET Framework, but was ingested for some of the targets. You can ignore this.
@terrajobst Is there any way we can remove this assembly from the catalog? It produces many false negatives.
To reduce the confusion, .NET Framework has been removed from the default Target Platforms list for porting scenario since the porting is primarily for estimating the API gap from .NET Framework to .NET Core platforms anyway. It is not the root solution, but for improving customer experience with default setting.
