What the title says.
The API Browser, when told to go to .net 10 or 11, is redirecting to .net Framework 4.8.1 or earlier. This makes a lot of APIs unreachable.
May be happening for other frameworks as well. I did not test it beyond trying 3 different browsers and a handful of namespaces, all for .net 10 and 11.
Many namespaces seem to be affected.
Here are a few:
Many more were broken, too.
Tested in Firefox, Edge, and Chrome.
What the title says.
The API Browser, when told to go to .net 10 or 11, is redirecting to .net Framework 4.8.1 or earlier. This makes a lot of APIs unreachable.
May be happening for other frameworks as well. I did not test it beyond trying 3 different browsers and a handful of namespaces, all for .net 10 and 11.
Many namespaces seem to be affected.
Here are a few:
Many more were broken, too.
Tested in Firefox, Edge, and Chrome.