none
Can a single address entry be used for multiple client endpoints? RRS feed

  • Question

  • Have a client app which has a dozen service references. Each reference creates a single client endpoint in the app.config, all with the same address, such as below. I'd like to have the address once in the config file. Found base address for service, looking for something similar for client.

    <client>
      <endpoint address="http://host/psServiceListeningConnector"
        binding="basicHttpBinding" bindingConfiguration="[bindingConfig1]"
        contract="[contract1]"
        name="[name1]" />
      <endpoint address="http://host/psServiceListeningConnector"
        binding="basicHttpBinding" bindingConfiguration="[bindingConfig1]"
        contract="[contract2]"
        name="[name2]" /></client>

    Thursday, January 12, 2017 9:39 PM

All replies

  • Hi tallman5,

    >>Can a single address entry be used for multiple client endpoints?

    No, the base address only works on the server side, there’s nothing similar on the client side. On the client side, you always have to define the complete, full service address your endpoint should connect to.

    Best Regards,

    Edward


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, January 13, 2017 2:20 AM
  • Hi tallman5,

    Is there any issue in this thread? If not, I would suggest you mark the helpful reply as answer to close this thread.

    Best Regards,

    Edward


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, February 3, 2017 1:46 AM