saikiranakula-amzn
commented
1 year ago Hi orcunhanay, Thank you for bringing up the concern. The data we have in our datastore is also updated by crawling the nuget.org. Currently we show the apis as compatible, incompatible based on support for the package have with .netcore framework. Anything else other than this will be shown as unknown. In your case the package you are referring to has .NET standard support for which our recommendations are minimal. As per the thought provide to suggest by showing update to latest version rather than unknown depends on what the latest version of package is compatible with - https://www.nuget.org/packages/FakeItEasy (currently marked for only .NET5 and standard). We will take a look at these concerns and get back to you accordingly.
Hi,
We have a question about "unknown" state Nuget Packages. We are working on our customer projects with Porting Assistant for .Net tool. As an assessment result, some packages are unknown in the following. For Example FakeItEasy 5.1.0
We have developed a basic code, it is sending a search request to the Nuget search page and then searches netstandard and net6/net7 words on the page. As you know, the FakeItEasy 5.1.0 packages version is compatible .NetStandard. And .Net Standard 2.0 is compatible to compatible with many versions of .Net. When I asked you earlier, you mentioned that you decide whether a package is compatible, incompatible, or unknown by looking at your own database.
Instead of marking FakeItEasy version 5.1.0 as unknown, could the Porting Assistant for .Net tool advise us to use the latest version for FakeItEasy? We would like to let you know about this as feedback.
Porting Assistant assessment result;
FakeItEasy nuget page;
.Net Standard Page;