.NET Standard API表面在线参考

本文介绍了.NET Standard API表面在线参考的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我只是想弄清楚类型 System.Windows.Input.ICommand 是否是新.NET Standard的一部分。

I was just trying to figure out whether the type System.Windows.Input.ICommand is part of the new .NET Standard.

当项目目标设置设置为 .NETStandard1.0 时，我确实设法使用该类型来编译库（在使用可移植库API表面，包括.NET Core 1.0）。

I did manage to compile a library using the type when the project target setting was set to .NETStandard1.0 (it also works when using a broad portable library API surface including .NET Core 1.0).

因此，尽管名称空间暗示WPF参与其中，并且名称空间未在 CoreFX文档的这一部分似乎在其中。

So, despite the odd namespace suggesting WPF involvement, and despite the namespace not being listed at this section of a CoreFX document it appears to be in it.

我想知道是否还有一个更易于访问的参考文献

I wonder if there's also a more accessible reference one can browse to see what API is supported rather than just trying it.

此外，API表面现在是否已修复，或者将来可以更改吗？换句话说，我所做的测试是否真的给了我权威的答案？

Also, are the API surfaces fixed now, or can this change in the future? In other words, does the test I made give me an authoritative answer at all?

推荐答案

> docs.microsoft/en-us/dotnet/core/api/index 具有.NET Core 1.0中所有内容的文档（不包括技术上不同的ASP.Net Core）。该文档站点涵盖netstandard1.6 / netcoreapp1.0;但是我不觉得有办法知道何时在较低版本的netstandard中不提供类型/成员，因此当您降低netstandard版本（这会增加兼容平台的数量）时，某些API可能会消失（成为编译错误） ）。

docs.microsoft/en-us/dotnet/core/api/index has documentation for everything that was in .NET Core 1.0 (not including ASP.Net Core, which is technically a different product). That documentation site covers netstandard1.6 / netcoreapp1.0; but I don't offhand see a way to know when a type/member isn't available in lower versions of netstandard, so as you decrease your netstandard version (which increases the number of compatible platforms) some APIs might disappear (becoming compile errors).

netstandard1.0到netstandard1.6是稳定的，不会从其中删除任何内容，也不会在上添加任何内容（可以添加其他软件包，使它们具有最小的依赖关系，但这是netstandard版本上的新API 。

netstandard1.0 through netstandard1.6 are stable, nothing will be deleted from them, and nothing will be added to them (new additional packages could be added which have them as the minimum dependency, but that's new API on a netstandard version).