.NET Portability Analyzer 与 .NET API Browser 结果不匹配 [英] .NET Portability Analyzer doesn't match .NET API Browser results
问题描述
我在 .NET Portability Analyzer(VS 扩展)和官方 .NET API 浏览器之间产生了冲突的结果:
这表明该类型仅在即将发布的 .NET Core 3.0 版本中可用.但是，在使用上述 API 浏览器时，它明确指出该类型已在 .NET Core 2.0 版中可用.
我更喜欢信任 API 浏览器，但我只是想知道是否有人对可移植性分析器给出的输出有不同的解释.
这有点棘手.该类型将是 .NET Core 3.0 的一部分，它不作为 .NET Core 2.0 或 2.1 的一部分提供，但可通过额外的 NuGet 包 (System.Security.Permissions).
工具和文档可能对什么是特定版本的 .NET Core 的一部分"以及在特定版本上以某种方式可用"的内容有不同的看法.
您可以检查的另一个来源是 apisof.net:https://apisof.net/catalog/System.Security.Permissions.FileIOPermissionAccess正确地将类型列为 .NET Core 3.0 和.NET Core + Platform Extensions"2.0 和 2.1
I have a conflicting results between the .NET Portability Analyzer (VS extension) and the official .NET API Browser: https://docs.microsoft.com/en-us/dotnet/api
When analyzing a .NET Framework assembly with the portability analyzer, I have the following result for the type System.Security.Permissions.FileIOPermissionAccess:
This would suggest that the type is only available in the upcoming 3.0 release of .NET Core. However when using the aforementioned API browser, it clearly states that the type is already available in version .NET Core version 2.0.
I prefer to trust the API browser, but I just wondered if anyone had a different interpretation of the output given by the portability analyzer.
This is a bit tricky. The type will be part of .NET Core 3.0, it does not ship as part of .NET Core 2.0 or 2.1, but is available via an additional NuGet package (System.Security.Permissions).
The tools and documentation may have a different view on what is "part of" a particular version of .NET Core and what is "usable" in some way on a particular version.
An additional source you can check is apisof.net: https://apisof.net/catalog/System.Security.Permissions.FileIOPermissionAccess which correctly lists the type as .NET Core 3.0 and ".NET Core + Platform Extensions" 2.0 and 2.1
这篇关于.NET Portability Analyzer 与 .NET API Browser 结果不匹配的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
