System.Net.Quic is not trimmed on mobile platforms

[marek-safar]

System.Net.Quic is not supported except on Windows but still cannot be trimmed because it's initialized aggressively via static constructors even on platforms that don't support it like iOS or android. Initialization chain is like

	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.ctor
	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.cctor
	  at System.Net.Quic.Implementations.MsQuic.MsQuicImplementationProvider:get_IsSupported
	  at System.Net.Http.HttpConnectionPool:.ctor
	  at System.Net.Http.HttpConnectionPoolManager:SendAsyncCore
	  at System.Net.Http.HttpConnectionPoolManager:SendAsync
	  at System.Net.Http.HttpConnectionHandler:SendAsync

There is IsSupported property but it does not conform to the recommended Feature switch setup so it cannot be used either.

@eerhardt @karelz

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

Issue Details

---

System.Net.Quic is not supported except on Windows but still cannot be trimmed because it's initialized aggressively via static constructors even on platforms that don't support it like iOS or android. Initialization chain is like

	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.ctor
	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.cctor
	  at System.Net.Quic.Implementations.MsQuic.MsQuicImplementationProvider:get_IsSupported
	  at System.Net.Http.HttpConnectionPool:.ctor
	  at System.Net.Http.HttpConnectionPoolManager:SendAsyncCore
	  at System.Net.Http.HttpConnectionPoolManager:SendAsync
	  at System.Net.Http.HttpConnectionHandler:SendAsync

There is IsSupported property but it does not conform to the recommended Feature switch setup so it cannot be used either.

@eerhardt

Author:	marek-safar
Assignees:	-
Labels:	area-System.Net, untriaged
Milestone:	-

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

Issue Details

---

System.Net.Quic is not supported except on Windows but still cannot be trimmed because it's initialized aggressively via static constructors even on platforms that don't support it like iOS or android. Initialization chain is like

	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.ctor
	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.cctor
	  at System.Net.Quic.Implementations.MsQuic.MsQuicImplementationProvider:get_IsSupported
	  at System.Net.Http.HttpConnectionPool:.ctor
	  at System.Net.Http.HttpConnectionPoolManager:SendAsyncCore
	  at System.Net.Http.HttpConnectionPoolManager:SendAsync
	  at System.Net.Http.HttpConnectionHandler:SendAsync

There is IsSupported property but it does not conform to the recommended Feature switch setup so it cannot be used either.

@eerhardt

Author:	marek-safar
Assignees:	-
Labels:	area-System.Net.Quic, untriaged
Milestone:	-

Tagging subscribers to 'size-reduction': @eerhardt, @SamMonoRT, @marek-safar
See info in area-owners.md if you want to be subscribed.

Issue Details

---

System.Net.Quic is not supported except on Windows but still cannot be trimmed because it's initialized aggressively via static constructors even on platforms that don't support it like iOS or android. Initialization chain is like

	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.ctor
	  at System.Net.Quic.Implementations.MsQuic.Internal.MsQuicApi:.cctor
	  at System.Net.Quic.Implementations.MsQuic.MsQuicImplementationProvider:get_IsSupported
	  at System.Net.Http.HttpConnectionPool:.ctor
	  at System.Net.Http.HttpConnectionPoolManager:SendAsyncCore
	  at System.Net.Http.HttpConnectionPoolManager:SendAsync
	  at System.Net.Http.HttpConnectionHandler:SendAsync

There is IsSupported property but it does not conform to the recommended Feature switch setup so it cannot be used either.

@eerhardt @karelz

Author:	marek-safar
Assignees:	-
Labels:	area-System.Net.Quic, size-reduction, untriaged
Milestone:	-

[geoffkizer]

What needs to happen to fix this?

Note, S.N.Quic is also supported on Linux and eventually on MacOS as well.

[eerhardt]

What needs to happen to fix this?

I think the initial thinking is to change MsQuicImplementationProvider:get_IsSupported to conform to a feature-switch. See other implementations for reference like

• EventSource.IsSupported
• EnableUnsafeBinaryFormatterSerialization

The idea being that vertical app models that want to disable/trim certain features can set these feature switches in their MSBuild Sdk files. So here Xamarin can set System.Net.Quic.IsSupported=false and all the Quic implementation will get trimmed away by the linker in a Xamarin app.

[geoffkizer]

The MsQuicImplementationProvider:get_IsSupported API isn't intended to ship; it's just a temporary measure while we have multiple providers that we are developing/testing with.

I suspect what we want is something like a single public static bool IsSupported on some top-level QUIC class (maybe QuicConnection? not sure).