.NET Standard API Reference
<h2>UPDATE:</h2>

<p>So it seems to be an <a href="https://github.com/dotnet/docs/issues/772" rel="nofollow noreferrer">open issue</a> now. So I guess until this is done I will have to rely on <a href="https://docs.microsoft.com/en-us/dotnet/core/api/index" rel="nofollow noreferrer">.NET Core API reference</a> and pray I won't hit one of the <code>43 APIs that .NET Framework 4.6.1 doesn't support</code> but are officially supposed to be...</p>

<p>Also relying on .NET Core API reference and considering the same as .NET standard could be badly surprising. For example when I take a look at the namespace list I can see <code>System.Drawing</code> but when clicking on it, we then realize this is an <a href="https://docs.microsoft.com/en-us/dotnet/api/system.drawing?view=netcore-1.0" rel="nofollow noreferrer">almost empty namespace</a> containing only 6 structures.</p>

<p>Are there several namespaces like this? I don't know, I have to compare .NET core and .NET Framework documentation to get the answer.</p>

<h2>ORIGINAL POST:</h2>

<p>I'm trying to find the .NET Standard API reference.</p>

<p>On <a href="https://docs.microsoft.com/en-us/dotnet/index" rel="nofollow noreferrer">this page</a> there are only links to <code>.NET Core API reference</code> and <code>.NET Framework API reference</code>.</p>

<p>Yes I've searched and I've read others SO questions. For example <a href="https://stackoverflow.com/a/40405198/1203116">this answer</a> points to .NET Core API reference instead of .NET standard and the same in this <a href="https://github.com/dotnet/corefx/issues/10099#issuecomment-233129946" rel="nofollow noreferrer">Github issue feed</a></p>

<p>But .NET Core and .NET Standard are different. .NET Core is the implementation of .NET Standard APIs.</p>

<p>One of the big problem I see here is for example based on the <a href="https://docs.microsoft.com/en-us/dotnet/articles/standard/library" rel="nofollow noreferrer">official documentation</a> .NET Framework 4.6.1 will implement .NET Standard 2.0</p>

<p><a href="https://i.stack.imgur.com/CVgym.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CVgym.png" alt="enter image description here"></a></p>

<p>Ok great, except that the <a href="https://github.com/dotnet/standard/blob/master/docs/netstandard-20/README.md" rel="nofollow noreferrer">.NET Standard Github readme page</a> is also saying</p>

<blockquote>
  <p>On the other hand, .NET Standard 2.0 adds many APIs that .NET Framework 4.6.1 already supports. The delta looks as follows:</p>
  
  <ul>
  <li><p>.NET Standard 2.0 adds 14,994 APIs that .NET Framework 4.6.1 already supports</p></li>
  <li><p><strong>.NET Standard 2.0 only has 43 APIs that .NET Framework 4.6.1 doesn't support
  Originally, we planned to simply elide those APIs from .NET Standard 2.0 in order to make it easier to understand what will work on .NET Framework 4.6.1.</strong></p></li>
  </ul>
  
  <p>However, we got a lot of feedback around this. You told us that this decision makes it really hard to reason about .NET Standard versioning rules. Thus, we decided to simplify this:</p>
  
  <ul>
  <li><p>.NET Standard 2.0 will be a strict superset of .NET Standard 1.6. In other words, no breaking changes will happen between .NET Standard 2.0 and 1.x.</p></li>
  <li><p>.NET Framework 4.6.1 will allow referencing binaries that are compiled against .NET Standard 2.0.
  Considering the number of APIs that .NET Framework 4.6.1 will not support is low and that these are all brand-new APIs with low adoption we believe this is a much better trade-off.</p></li>
  </ul>
  
  <p>You can use API Port to scan a given application to make sure no code in your application depends on these APIs.</p>
</blockquote>

<p>So what? Their solution to this problem is <code>to scan a given application</code>? So if I start a new project, giving the fact that I don't have code written yet, I would target .NET Standard and pray I don't end up with unsupported APIs that are supposed to be?</p>

<p>Also, are there other cases like this in other frameworks like Xamarin or UWP? What does that mean <code>vNext</code> exactly in the 2.0 column? Should I be worried of other unsupported APIs in other frameworks because <code>Considering the number of APIs that [Framework name] will not support is low and that these are all brand-new APIs with low adoption we believe this is a much better trade-off</code>?</p>

<p>The closest answer I can find to this question is by looking at the <a href="https://www.nuget.org/packages/NETStandard.Library/1.6.1" rel="nofollow noreferrer">NETStandard.Library NuGet package</a>'s dependencies. However that gives me dependencies of the 1.3 version (not 1.6 or I don't really understand this section), and that doesn't give me APIs reference of the next 2.0 which are supposed to be already determined.</p>

<p>Can't we have a full documented list of APIs <strong>really</strong> supported for each .NET Standard version? The only goal of .NET Standard is to provide developers this very important information, so why can't I find it?</p>