WCF configuration file: why do we need the clientBaseAddress database in the binding section?

There are three sections in the WCF configuration for a service client: Look at bindings => clientBaseAddress

Why do we need to provide a callback address? Is this field required? Why can't .NET determine the client address? Does this mean that I can indicate the client endpoint located on some other machine?

<configuration> <system.serviceModel> <client> <endpoint address= </client> <bindings> <wsDualHttpBinding> <binding name= clientBaseAddress= maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" </binding> </wsDualHttpBinding> </bindings> <behaviors> <endpointBehaviors> <behavior name=> </behavior> </endpointBehaviors> </behaviors> </system.serviceModel> 
+4
source share
1 answer

since you are using wshttpdualbinding, you will need ClientBaseAddress if you are running Windows XP. If you are not using XP, you can leave it.

See here for more information: http://blogs.msdn.com/b/wenlong/archive/2006/10/19/how-to-use-wsdualhttpbinding-on-windows-xp-for-hosted-services. aspx

+2
source

Source: https://habr.com/ru/post/1311423/


All Articles