Migration to grpc-dotnet is not actually done

[jSharpWolf]

Describe the bug
The migration issue has been closed with release 2.0 (#348), however the migration is incomplete, and Grpc.Core is still being used. Thus using the ZbClient fails on M1 macs.

In this commit ee36df8 a new package was added, but the code hasn't been adjusted to use the new package. Instead, the "Grpc" dependency has not been changed (2.46.6) and still uses Grpc.Core

To Reproduce
Check in IDE - it clearly still refers to Grpc.Core:

or

Try to connect to a Zeebe broker on M1 macs

Expected behavior
The client should not depend on Grpc.Core. The Grpc Nuget package should not be listed in the Client.csproj.

The classes also differ, this is how it should be:

Instead of using "Channel" "GrpcChannel" must be used, instead of using "ChannelOptions" GrpcChannelOptions" must be used

[ChrisKujawa]

Interesting! Thanks for the report, I must have overseen this somehow sorry. I try to take a look as soon as I can.

[xlegalles]

Interesting! Thanks for the report, I must have overseen this somehow sorry. I try to take a look as soon as I can.

You can take a look at the PR I did, and use GrpcChannel instead: https://github.com/camunda-community-hub/zeebe-client-csharp/pull/517/files#diff-9e614288d9ef8da794637095109c1ce073b0b71ca5cac3eddff724531f931f56

Also, note that we use v2.0 in production on Linux Ubuntu and all is fine until now.

[ChrisKujawa]

@jSharpWolf thanks for reporting! It should be fixed with the latest release https://github.com/camunda-community-hub/zeebe-client-csharp/releases/tag/2.1.0

I migrated to the new Grpc.net.GrpcChannel and had to migrate several other things, but it should be done now. Be aware Grpc.Core will not completely go away, since it contains several utilities which are also used in Grpc.net.