如何在未知契约类型时调用WCF服务中动态添加的Ping方法？

我正尝试在WCF中实现健康监测。服务端通过自定义服务宿主，在现有契约操作中添加了“Ping”操作。客户端需在未知契约类型的情况下调用该动态添加的Ping方法，但尝试的代码无法正常运行。

客户端代码 #

var channel = GetServiceProxy(); 
var result = channel.Ping();

[ServiceContract(Namespace = "http://tempuri.org/")] 
public interface IDynamicPing 
{
    [OperationContract(Action = "http://tempuri.org/Ping")] 
    string Ping(); 
}

public static IDynamicPing GetServiceProxy() 
{ 
    var binding = new NetNamedPipeBinding(NetNamedPipeSecurityMode.None); 
    binding.MaxReceivedMessageSize = 9999999; 

    var endpoint = new EndpointAddress("net.pipe://localhost/SampleWcfCustomerService/Service.svc"); 

    ChannelFactory<IDynamicPing> factory = new ChannelFactory<IDynamicPing>(binding, endpoint); 

    return factory.CreateChannel(endpoint); 
}

服务端web.config配置 #

<services>   
    <service name="SampleWcfServer.CustomerService">     
        <endpoint 
            address="" 
            binding="netNamedPipeBinding" 
            bindingConfiguration="ClientBinding"
            contract="CommonServices.ICustomerService">     
        </endpoint>   
    </service> 
</services>

<bindings>   
    <netNamedPipeBinding>     
        <binding name="ClientBinding" 
                 maxReceivedMessageSize="9999999">       
            <security mode="None"></security>     
        </binding>   
    </netNamedPipeBinding> 
</bindings>

调用错误信息 #

The message with Action 'http://tempuri.org/Ping' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

疑问 #

是否存在无需知晓契约即可调用服务方法的方式？或者能否通过反射实现？

一、当前错误的核心原因 #

你遇到的ContractFilter不匹配，是因为服务端对外暴露的ICustomerService契约中未声明Ping操作——哪怕你通过自定义宿主动态添加了该操作，WCF端点调度器仍会校验客户端与服务端的契约一致性。要让现有代码运行，要么在服务端的ICustomerService中正式添加Ping操作，要么服务端额外暴露一个包含Ping操作的独立端点。

二、无需预定义契约的调用方式 #

1. 直接发送原始Message #

通过IClientChannel手动构造并发送请求消息，完全不需要依赖契约接口：

public static string SendPingMessage()
{
    var binding = new NetNamedPipeBinding(NetNamedPipeSecurityMode.None);
    binding.MaxReceivedMessageSize = 9999999;
    var endpoint = new EndpointAddress("net.pipe://localhost/SampleWcfCustomerService/Service.svc");

    var factory = new ChannelFactory<IClientChannel>(binding, endpoint);
    var channel = factory.CreateChannel();
    channel.Open();

    // 构造Ping请求消息，指定对应Action
    var request = Message.CreateMessage(binding.MessageVersion, "http://tempuri.org/Ping");
    // 发送请求并接收响应
    var response = channel.Request(request);

    // 解析响应内容
    var result = response.GetBody<string>();

    channel.Close();
    factory.Close();
    return result;
}

2. 使用ChannelFactory<object>动态调用 #

利用WCF对object类型通道的支持，通过反射Invoke指定Action调用方法：

public static object CallPingWithoutContract()
{
    var binding = new NetNamedPipeBinding(NetNamedPipeSecurityMode.None);
    binding.MaxReceivedMessageSize = 9999999;
    var endpoint = new EndpointAddress("net.pipe://localhost/SampleWcfCustomerService/Service.svc");

    var factory = new ChannelFactory<object>(binding, endpoint);
    var channel = factory.CreateChannel();

    // 调用动态添加的Ping方法，通过Action匹配
    var result = channel.GetType().InvokeMember(
        "*",
        System.Reflection.BindingFlags.InvokeMethod | System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.Public,
        null,
        channel,
        new object[] { Message.CreateMessage(binding.MessageVersion, "http://tempuri.org/Ping") }
    );

    ((IClientChannel)channel).Close();
    factory.Close();
    return result;
}

三、反射调用现有代理 #

如果已经持有ICustomerService的代理实例，可以尝试通过反射调用动态添加的Ping方法——但这种方式可靠性较低，仅当服务端自定义宿主确保代理类型包含该方法时有效：

// 假设GetCustomerServiceProxy()返回ICustomerService的代理实例
var customerChannel = GetCustomerServiceProxy();
var pingResult = customerChannel.GetType().InvokeMember(
    "Ping",
    System.Reflection.BindingFlags.InvokeMethod | System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.Public,
    null,
    customerChannel,
    null
);

四、更推荐的健康监测方案 #

WCF自带成熟的健康监测能力，比如通过配置ServiceHealthBehavior暴露健康状态，或使用DiscoveryClient探测服务存活状态，无需手动添加Ping操作。如果一定要自定义Ping，建议服务端单独暴露一个健康监测专用端点，避免契约匹配问题。

内容的提问来源于stack exchange，提问作者shah harshil