-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grpc.Net.ClientFactory .NETStandard2.0 compatibility #1247
Comments
need .NETStandard2.0 support toooo |
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 |
Thank you for your help! |
so grpc.net.client does not support UWP? |
Grpc.Net.Client 2.36.0 is compatible with .netstandard2.0 so you can use it in UWP project. I only use grpc-web, because we have this project in Uno Platform, and compile it to webassembly, where we can't use grpc, only grpc-web. |
I have to set GrpcWebHandler as grpc httphandler in UWP app. here |
Ohh, I see! Microsoft will plan to support .netstandard2.1 and .net 5 for UWP, but don't know when. 21H1 os 21H2. We also wait for it. |
hope it won't be long. so sad. |
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:
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:
AsyncAuthInterceptor is not good for me, because it is called only before the function call.
The text was updated successfully, but these errors were encountered: