search

dotnet / wcf

This repo contains the client-oriented WCF libraries that enable applications built on .NET Core to communicate with WCF services.
MIT License
1.69k stars 556 forks source link

Client access for named pipe connection #3314

Closed tirth closed 5 years ago

tirth commented 5 years ago

Is it possible to include the NetNamedPipeBinding class for clients on .NET Core? We have a fairly substantial codebase that has a single remaining dependency on Framework specific code, which is accessing a key service out of our control that communicates via named pipes.

With .NET Core 3, we would like to move our WPF applications/libraries that currently have to target net461 over to netcoreapp/netstandard, as things like self contained deployment would be very beneficial.

As it is Windows specific, having access through the Windows Compatibility Pack would also work.

Lxiamail commented 5 years ago

@tirth thank you for your suggestion. We will prioritize this request with the other feature request based on customer votes. In the meantime, do you use NetTcpBinding instead?

tirth commented 5 years ago

Unfortunately the service only uses named pipes, so NetTcpBinding won't work for our use case, but glad to know it's being worked on!

Lxiamail commented 5 years ago

Closing this issue and use #2535 to track the same issue.

rsankardayal commented 4 years ago

Dynamics GP eConnect has a WCF service with an netnamedpipebinding endpoint (net.pipe://localhost...). I am very much interested if there is a solution to consume this service with .Net Core.

Is there any way this class could be added to the compatibility pack?