Closed bentoi closed 3 years ago
Tagging subscribers to this area: @dotnet/ncl See info in area-owners.md if you want to be subscribed.
Author: | bentoi |
---|---|
Assignees: | - |
Labels: | `area-System.Net.Quic`, `untriaged` |
Milestone: | - |
How did you get msquic? It is not included in the runtime. Also example of you are trying to do would be helpful. On Windows, QUIC also depends on very recent Windows versions (like Insider Preview) and it will not run without proper Schannel support. Also there will not be QUIC api in .NET 6. The only one way how to console it will be via HTTP/3.
I expected msquic to be included in the runtime. So this error is the result of msquic not being present? I'm trying to see if we can use Quic as a transport. Since the API is included in the .NET 6 preview documentation, I expected it would be useable without having to use HTTP/3.
The story is complicated and you can try to build msquic yourself from https://github.com/microsoft/msquic/blob/main/docs/BUILD.md
QUIC API will not be public when 6.0 - ships as we don't have confidence we can make it 1st class citizen. It is still on TODO list and it will come come in some later release.
We plan to remove it from public API surface as part of .NET 6 Preview 7. We will bring it back after we ship/fork for .NET 7.
See #54534
Description
I tried a sample program to create a Quic connection with .NET 6 preview 4. It fails on both macOS and Windows with a
NullReferenceException
:Configuration
macOS / Windows with .NET Core 6 preview 4
Other information
When building the program I get the following messages: