-
Notifications
You must be signed in to change notification settings - Fork 56
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
Migrate to grpc-dotnet #348
Comments
Hey @Zelldon, it has been a long time since there has been a release of a new version. What is you policy regarding not falling to for behind software updates? My bootstrap project is highly dependent of your project and I would regret to see that it will be failing because of this. For the time being could you add Apple M1 support to your project? (https://github.com/einari/Grpc.Core.M1) Hopefully you will be able to release a new version which will fix a lot of issues including this one. Thanks! Arjan |
Tbh I was also thinking for a while to create a new release but always miss it. I try to do it soon. Please remind me if I miss it again |
Hi @Zelldon, now that .net 3.1 has already reached EOL, developers naturally look forward to code with .net 6.0 & Above. But the zb-client library has an internal dependency on Grpc.core, this has to be migrated to grpc-dotnet Without this support in the C# client, we are forced to stick to .net core 3.1 on the MAC, since the native Grpc library in C# is not available for arm based images. |
Can we help? (contribute) |
Hey @xlegalles, absolutely, contributions are welcome! |
I've pushed a PR #517 |
deps(client): uses Grpc.Net instead of Grpc.Core fix: camunda-community-hub#348
deps(client): uses Grpc.Net instead of Grpc.Core fix: camunda-community-hub#348
Is your feature request related to a problem? Please describe.
https://grpc.io/blog/grpc-csharp-future/
Describe the solution you'd like
Describe alternatives you've considered
Stick with the grpc-core
Additional context
This would solve #194
The text was updated successfully, but these errors were encountered: