TypedHeader has linker unfriendly logic

[davidfowl]

I'm not sure how common this logic is but it feels like we can remove it and not break anyone..

aspnetcore/src/Http/Http.Extensions/src/HeaderDictionaryTypeExtensions.cs

Line 216 in 983e7ed

return GetListViaReflection<T>(values);

C:\dev\git\aspnetcore\src\Http\Http.Extensions\src\HeaderDictionaryTypeExtensions.cs(223,13): Trim analysis warning IL2006: Microsoft.AspNetCore.Http.HeaderDictionaryTypeExtensions.GetViaReflection<T>(String): The field 'System.Type Microsoft.AspNetCore.Http.HeaderDictionaryTypeExtensions/<>c__DisplayClass11_0`1::type' with dynamically accessed member kinds 'None' is passed into the implicit 'this' parameter of method 'System.Type.GetMethods(BindingFlags)' which requires dynamically accessed member kinds 'NonPublicMethods | PublicMethods'. To fix this add DynamicallyAccessedMembersAttribute to it and specify at least these member kinds 'NonPublicMethods | PublicMethods'. [C:\Users\davifowl\source\repos\WebApplication60\WebApplication60\WebApplication60.csproj]

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[JamesNK]

Fixed via #40561