QUIC: Aquiring msquic.dll on Windows and Linux

[JamesNK]

There was an experimental Quic package that included msquic.dll for .NET 5. You could add that to your app to get the right msquic.dll version.

With .NET 6 today you must build msquic.dll and then copy it to the runtime location.

This is blocking integration testing and benchmarking in CI and perf environments.

• Decide how msquic.dll will be acquired on Windows
• Implementation

[ghost]

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

Issue Details

---

There was an experimental Quic package that included msquic.dll for .NET 5. You could add that to your app to get the right msquic.dll version.

With .NET 6 today you must build msquic.dll and then copy it to the runtime location.

The issue is for figuring out how msquic.dll will be acquired on Windows and implementing it.

This is blocking integration testing and benchmarking in CI or perf environments.

Author:	JamesNK
Assignees:	-
Labels:	area-System.Net.Quic
Milestone:	-

[ManickaP]

@wfurt So we have officialy published linux packages, we're binplacing on Windows, can this be closed? Are we missing something still?

[JamesNK]

Is information about using the Linux package published somewhere?

[ManickaP]

Officially no, not yet, we should put that in docs though.
Do you personally want that now? I can forward you the mail.

[JamesNK]

Not urgently. Update instructions about msquic in the readme and I'll figure it out from that.

[ManickaP]

Docs updated: https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Quic/readme.md

This is resolved.

[JamesNK]

Re-opening as we don't see msquic.dll in the runtime directory (Windows SDK)

We've checked 6.0.0-preview.7.21360.10 and 6.0.0-preview.7.21362.3.

[JamesNK]

[ManickaP]

@JamesNK @wfurt : I think we can close this now, ASP.NET Core is getting the dll. Or is there still some problem?
Note that we have the rest of the packaging work covered in #55639

[wfurt]

Let's close this as dup of #55639.
The new issue has more details and tracks remaining work.