I have an application using discovery that may be deployed locally on the same PC or remote from the service it consumes. Is there any way to expose the named pipe binding via WCF discovery? If not I suppose I can negotiate after the service is discovered to determine the most suitable binding.
Share
Yes, it’s possible to do that. But since the address will be listed as “localhost” (the only possible address for net.pipe), you’ll likely need some sort of test to verify that the service is actually running on the same machine as the discovery client.