Originally reported by @polewskm at https://github.com/dotnet/docs/issues/2311
The documentation of Hash鈥婣lgorithm in the following target frameworks incorrectly mentions that it has an base interface of ICryptoTransform when this is not true:
If you browse the source for [HashAlgorithm.cs] you can find that the interface ICryptoTransform is only added for __.NET Standard 2.0__
I would attempt a PR to fix the documentation mistake but I do not know how to show different base interfaces for the combination of target frameworks.
From @rpetrusha: Thanks for opening this issue, @polewskm. The list of implemented interfaces is auto-generated using reflection. However, currently it does not take into account platform or version differences in interface implementation. We've opened an internal bug, #996154, to address this issue.
From @mairaw: @rpetrusha the internal bug referred here was about the list of interfaces not being complete, but I didn't see information about per version in that same bug. Perhaps you opened a different bug for this?
@dend are you aware of any bugs tracking this request?
Another case where the wrong interfaces are displayed @dend
https://github.com/dotnet/docs/issues/5203
More issues are being reported for this:
https://github.com/dotnet/docs/issues/5608
https://github.com/MicrosoftDocs/feedback/issues/226#issuecomment-382851106
@dend do we have an issue logged?
Closing this in favor of #226 - let's keep the conversation there.
Should this be reopened? As has been pointed out in this blog post, the issue is still not fixed. And the "duplicate" https://github.com/MicrosoftDocs/feedback/issues/226 was closed, because it was mostly about content, which doesn't belong in this repo. But that means it was not really a duplicate, because this issue is about infrastructure, which belongs here.
Yes, we should reopen
馃殌 ATTENTION: Internal request logged.
I have run into this several times in the last two weeks.
This looks like an mdoc bug @joelmartinez given the XML doesn't show alternative signatures.
@mairaw there is working scheduled to begin very soon that will address this very issue :D
Most helpful comment
@mairaw there is working scheduled to begin very soon that will address this very issue :D