Ben Olden-Cooligan

I'll note that #1117 should also fix some macOS SANE scanning issues in #919.

Hi, As this is a personal project with no official support, I can't provide guarantees, though I do intend to keep it up to date for compatibility with gRPC and...

If you're willing to use some reflection, something like this should work: ```c# var def = Greeter.BindService(new GreeterService()); var def2 = def.Intercept(...); // Needs a Grpc.Core reference def2.BindService(server.ServiceBinder); // BindService...

Thanks for the link, I didn't realize that had been implemented - Unix domain sockets should be comparable to named pipes, providing you're using Windows 10. This library will still...

I think those classes can just be made internal with no issue. As far as logging, my idea was to have an [ILogger](https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.ilogger?view=dotnet-plat-ext-3.1) property on the options classes.

I'd prefer to have easier compatibility. Microsoft.Extensions.Logging is commonly used (e.g. in grpc-dotnet) and has adapters for pretty much every logging framework. Plus it's easy to use extra functionality (e.g....

Well, as far as big libraries, there's [Grpc.Net.Client](https://www.nuget.org/packages/Grpc.Net.Client) :). Specifically the [package](https://www.nuget.org/packages/Microsoft.Extensions.Logging.Abstractions) isn't a logging framework but an abstraction that can be used with any framework. It's certainly a fair...

Yeah, actually some kind of Error event on the server/channel objects would probably do the trick.

It might be related to this? https://stackoverflow.com/questions/46683772/issue-with-net-core-named-pipes-on-linux-address-already-in-use

I can consider changing the defaults, but there is a client timeout option: https://github.com/cyanfish/grpc-dotnet-namedpipes/blob/043cead5ba3d0e3fb746160dc7e71729a66d657c/GrpcDotNetNamedPipes/NamedPipeChannelOptions.cs#L40