Grpc.Net.ClientFactory .NETStandard2.0 compatibility

Is your feature request related to a problem? Please describe.

I hava an UWP project which uses Grpc.Net.Client.Web 2.36.0. I see, that this version supports .NETStandard2.0, but the
Grpc.Net.ClientFactory only supports .NETStandard2.1 and net5.0. The UWP doesn’t support 2.1 or .net5 yet.

My problem is I would like to use interceptors for the client side, according to this code:

services
    .AddGrpcClient<Greeter.GreeterClient>(o =>
    {
        o.Address = new Uri("https://localhost:5001");
    })
    .AddInterceptor(() => new SomeInterceptor())   

Describe the solution you’d like

Grpc.Net.ClientFactory .NETStandard2.0 compatibility

Describe alternatives you’ve considered

Closely enough to me that add multiple interceptor with somewhere on these lines:

CallCredentials callCredentials = CallCredentials.FromInterceptor(CHttpClientService.AsyncAuthInterceptor);
    return GrpcChannel.ForAddress(Settings.CSettings.ServerAddress, new GrpcChannelOptions
    {
        HttpHandler = new GrpcWebHandler(new CHttpClientService().PrepareHttpMessageHandler()),
        Credentials = ChannelCredentials.Create(new SslCredentials(), callCredentials),
    });

AsyncAuthInterceptor is not good for me, because it is called only before the function call.

[JamesNK]

netstandard2.0 client factory will be in the next release.

You can add interceptors like this to a channel without client factory:

var channel = GrpcChannel.ForAddress("https://blah");
var invoker = channel.Intercept(new SomeInterceptor());

var client = Greeter.GreeterClient(invoker);

The extension method is in Grpc.Core.Interceptors.ChannelExtensions.

[HppZ]

hope it won’t be long. so sad.