如何使用自定义序列化WCF？

Question

Has any one ever implemented a custom serializer in WCF ? The reason i want to replace the WCF default serializer with custom serializer is to call different services from the same wcf proxy client.I would be glad if some one can suggest a way to do this ?

Answer 1

I did something similar on a project I recently did.

However I did have 2 different WCF clients. How I "switched" was I then created a shared interface between the clients and then used a ServiceLocator to fetch the IClient .

Does this make sense?

Answer 2

If I understand the problem correctly you have an application that you want to talk to one of two services that use the same interface based on some criteria. The services have different configurations so you cannot reuse the same config.

To tackle this I would setup the two configurations in the application config, it could also be done in code if you wish.

<client>
  <endpoint address="http://service1"
            binding="basicHttpBinding"
            bindingConfiguration="Service1Binding"
            behaviorConfiguration="Service1Behavior"
            contract="IServiceInterface, Service"
            name="Service1"/>

  <endpoint address="http://service2"
            binding="basicHttpBinding"
            bindingConfiguration="Service2Binding"
            behaviorConfiguration="Service2Behavior"
            contract="IServiceInterface, Service"
            name="Service2"/>
</client>

In your code you then need some sort of conditional statement to determine which service you want to talk to. Once you have done this you can create a ChannelFactory for the required configuration.

string serviceName = FullMoon ? "Service1" : "Service2";

var channelFactory = new ChannelFactory<IServiceInterface>(serviceName);

var proxy = channelFactory.CreateChannel();

proxy.SomeServiceCall();

channelFactory.Close();

If you are using IoC to inject the proxy you will probably need to push this into some sort of factory. You can also look at optimizing this as creating the ChannelFactory is the expensive part, it is possible to create the Factory without specifying the configuration just the contract. You would then need to specify the binding and the endpoint when you create the channel.