API reference doesn't show members for .Net Standard types not referenced from NETStandard.Library

[svick]

For types that have .Net Standard packages, but are not part of NETStandard.Library, it seems the new API reference behaves as if those types did not have .Net Standard versions at all (i.e. it hides all their members).

For example, this happens for XmlNode (the URL says netstandard-1.6, but it seems it changes to netframework-4.7 on its own, so you have to use the dropdown to see it), which exists in the System.Xml.XmlDocument package, which has a version for .Net Standard 1.3.

I think for such types, their .Net Standard version should be shown.

https://apisof.net/ has a very similar issue (https://github.com/terrajobst/apisof.net/issues/2), which could be related.

[mairaw]

@dend can you look at this? It seems that selecting .NET standard is not sticky.

[mairaw]

@svick I know this is way older than #3132, but they seem to be regarding the same issue. Is it ok to close this and track that issue on that one?

[svick]

@mairaw Of course. If it was up to me, I would probably choose the older issue or the more general one and this is both. But it's not. 🙂

[mairaw]

Yes, that's usually my approach. It's just we got the attention of the dev team on that one, so it will help move things. I'll make that one more generic. Thanks for your understanding.

[mairaw]

Reopening this one. The WCF one will be handled differently.

[mairaw]

According to the API Catalog (https://apisof.net/catalog/System.Xml.XmlNode), this is included as part of the .NET Standard + Platform Extensions. I know we had some plans to show NuGet info on docs that @dend was working on, but should we include the assemblies from that section (.NET Standard + Platform Extensions) into docs @terrajobst?

[carlossanlop]

Tagging @mimisasouvanh @joelmartinez @TianqiZhang for triaging.