Ben Olden-Cooligan

You can set NamedPipeChannelOptions.ConnectionTimeout and then call a method on the client and it should fail within that time if the server isn't responding.

It should throw an RpcException with StatusCode.Unavailable.

Thanks for the kind words! Looks like the client side is simple for both (just use NamedPipeChannel in place of `GrpcChannel.Create` in their samples). I had a look at protobuf-net.Grpc...

Hi, thanks for figuring that out! I'd merge a PR that uses NET5_0_OR_GREATER instead of NET5_0.

https://github.com/cyanfish/heltour/pull/396 merged

Sorry I didn't get to this until now, but this should be in 2.0.0 (along with some other changes listed in the changelog).

Linux (and Mac) support should now work in 2.0.0.

I added a 30s default timeout in 2.0.0.

I added such an event in 2.0.0.

You can set access controls (e.g. [CurrentUserOnly](https://github.com/cyanfish/grpc-dotnet-namedpipes/blob/e292e4c6d36c00321f4c60a8435d891999fe47e0/GrpcDotNetNamedPipes/NamedPipeServerOptions.cs#L26)). Aside from that I'm not sure there's a ton of point to encrypting a connection that doesn't go over the network. And as...