mex-bindings

How to force a net.tcp mex endpoint (mexTcpBinding) to participate in port sharing?

前提是你 提交于 2020-01-22 13:49:11
问题 I have a WCF service which is hosted as a Windows Service. We would like to enable a mex endpoint at the same address (but with a '/mex' suffix). I have been trying to do this (unsuccessfully) using the following configuration: <system.serviceModel> <services> <service name="MyCompany.MyService" behaviorConfiguration="defaultServiceBehavior"> <host> <baseAddresses> <add baseAddress="net.tcp://localhost"/> </baseAddresses> </host> <endpoint address="MyService" binding="netTcpBinding" contract=

“interface not found” in WCF Moniker without registration for excel

感情迁移 提交于 2019-12-12 03:44:34
问题 I'm trying to connect excel to a WCF service, but I can't seem to get even a trivial case to work... I get an Invalid Syntax error when I try and create the proxy in excel. I've attached the visual studio debugger to excel, and get that the real error is "interface not found". I know the service works because the test client created by visual studio is ok... so the problem is in the VBA moniker string. I'm hoping to find one of two things: 1) a correction to my moniker string that will make

How to force a net.tcp mex endpoint (mexTcpBinding) to participate in port sharing?

一笑奈何 提交于 2019-12-03 11:29:01
I have a WCF service which is hosted as a Windows Service. We would like to enable a mex endpoint at the same address (but with a '/mex' suffix). I have been trying to do this (unsuccessfully) using the following configuration: <system.serviceModel> <services> <service name="MyCompany.MyService" behaviorConfiguration="defaultServiceBehavior"> <host> <baseAddresses> <add baseAddress="net.tcp://localhost"/> </baseAddresses> </host> <endpoint address="MyService" binding="netTcpBinding" contract="MyCompany.IMyService" bindingConfiguration="netTcpBindingConfig" /> <endpoint address="MyService/mex"

Referencing WCF Services without mex binding

半腔热情 提交于 2019-11-27 07:58:46
问题 I was wondering how a client project in Visual Studio could reference a WCF service that doesn't have a mex binding. Whenever I remove the default mex binding in any sample WCF service, the client apps cannot find the service and in the auto-generated comments, it's recommended that in production environment, mex binding should be removed. Then how are the client apps supposed to find the service and reference it? 回答1: The mex endpoint is a necessary part of WCF SOAP services. It is what