"Recommended changes" should point users to Microsoft.Windows.Compatibility package where appropriate

[IanKemp]

Should you happen to have code that is using Windows-specific APIs such as the registry, event log, performance counters, etc. then ApiPort will not give you any advice on how to port that code.

But there is a NuGet package, Microsoft.Windows.Compatibility, that covers many of these missing APIs. Although it is prerelease, it's definitely an option that should be presented in the ApiPort report output - as these particular APIs are almost certain to be a sticking point for Windows projects trying to migrate to Standard or Core, and visibility of Microsoft.Windows.Compatibility is not great.

[twsouthwick]

@terrajobst Is the catalog marked with APIs that are available in the Microsoft.Windows.Compatibility pack?

[terrajobst]

The catalog does contains the packages that are part of the compat pack (they are part of the + Extension groups).

However, the catalog doesn't contain:

• Information which APIs throw PlatformNotSupportedException
• Information which packages you need to install

It would be great to add both, but so far we never had the cycles to do that :-(

[terrajobst]

Closing as API Port was deprecated in favor of binary analysis in .NET Upgrade Assistant.