Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

why there is so much more code? shouldn't "generator" have the opposite effect?

This code was generated from a generator that runs in a different mode and adapted to this use case. A source generator to capture this scenario is tracked in #63590. When that feature is implemented, we will move this code back to being source-generated.

@BrennanConroy is there any validation we can do to make sure I caught all the cases that are causing problems?

All we're doing in ASP.NET Core is calling QuicImplementationProviders.Default.IsSupported, so if you can run that successfully (maybe check it failed before) then it should be good.

Edit: No guarantee that the actual usage of MSQuic has issues after this change of course, but that'll be verified once we consume the fix.

It looks like there might be some more non-blittable marshalling places in MsQuic. Marking this as no-merge for now.

just a note that msquic now produce low-level generated binding for c#. There is desire to abandon ours and use theirs in 7.0 time frame.

I've fixed the last few cases that were causing issues. Once this is green, it's ready to merge.

just a note that msquic now produce low-level generated binding for c#. There is desire to abandon ours and use theirs in 7.0 time frame.

if eventually it will be replaced, what value this temporary excessive glue would bring (other than burdening the git history)?

The library is currently broken without this change, so it is necessary to enable ASP.NET to consume newer dotnet/runtime builds