dotnet / dotnet/dotnet-api-docs

API Browser redirecting to .net Framework 4.8.1 or earlier for a lot of APIs

Open
#12,614 16 comments 34 reactions 0 assignees View on GitHub
area-Infrastructure untriaged
Dominant language
C#
Stars
949
Forks
1.7k
Avg merge
3d 27m
Merged PRs (30d)
49

Description

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:
* [System](https://learn.microsoft.com/en-us/dotnet/api/system?view=net-10.0) - Goes to .net Framework 4.8.1
* [System.Buffers](https://learn.microsoft.com/en-us/dotnet/api/system.buffers?view=net-10.0) - Goes to netstandard 2.1
* [System.Buffers.Binary](https://learn.microsoft.com/en-us/dotnet/api/system.buffers.binary?view=net-10.0) - Goes to netstandard 2.1
* [System.Collections.Generic](https://learn.microsoft.com/en-us/dotnet/api/system.collections.generic?view=net-10.0) - Goes to .net framework 4.8.1, making things like [PriorityQueue](https://learn.microsoft.com/en-us/dotnet/api/system.collections.generic.priorityqueue-2?view=net-10.0) unreachable via the tree (I built the link myself)

Many more were broken, too.
Tested in Firefox, Edge, and Chrome.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.