MSDN > 論壇首頁 > Windows Azure > Configuration binding extension could not be found
發問發問
 

已答覆Configuration binding extension could not be found

  • 2009年7月2日 下午 03:25SANMI 使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     
    Hi! I'm still solving problems about this topic: http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/c217a52e-de4d-430c-adf0-e2033fae326a/#c4b3bd3b-06ff-4d1c-bde7-51133e7afc89

    I have done all the steps but I have gotten this erreur:

    Configuration binding extension 'system.serviceModel/bindings/BasicHttpRelayBinding' could not be found. Verify that this binding extension is properly registered in system.serviceModel/extensions/bindingExtensions and that it is spelled correctly.

    when SendActivity of the workflow try to comunicate to WCF service. My WCF Service is hosted out of Windows Azure (isn't in my web role).

    Also, in my solution there isn't a RelayClientAuthentication to put to "None". Where is this?

    I don't know where is the problem. If anybody could complete a guide to do it, it would be fantastic.

    Thank you!

解答

  • 2009年7月3日 上午 07:06Yi-Lun LuoMSFT, 版主使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     已答覆
    Hello, you mentioned the service is hosted out of Windows Azure. So I think it's hosted on your on-premise server, right? Then you don't need to use BasicHttpRelayBinding in your web role. You can use a normal BasicHttpBinding. Please remove any relay related bindings from your web.config.

    To set RelayClientAuthenticationType to None, please add the following configuration to your service project (not web role).

    <

     

    bindings>

    <

     

    basicHttpRelayBinding>

    <

     

    binding name="default">

    <

     

    security mode="None" relayClientAuthenticationType="None"/>

    </

     

    binding>

    </

     

    basicHttpRelayBinding>

     

     

    </bindings>


    Then make your endpoint to use the binding configuration:

    <

     

    endpoint binding="basicHttpRelayBinding" bindingConfiguration="default" .../>


    Web role does not need to perform this step. As long as RelayClientAuthenticationType is set to None on the service side, clients can connect to this service as if it is a normal WCF service.

    If you encoutered the above problem on the service side, can you confirm if you have installed .NET Services SDK? Please install the SDK. It will add some WCF extensions to the machine.config. Without SDK, you'll have to write all those extensions in the app.config. I would suggest you to install .NET Services SDK on the machine that is hosting your service.
    Lante, shanaolanxing This posting is provided "AS IS" with no warranties, and confers no rights.

所有回覆

  • 2009年7月3日 上午 07:06Yi-Lun LuoMSFT, 版主使用者勳章使用者勳章使用者勳章使用者勳章使用者勳章
     已答覆
    Hello, you mentioned the service is hosted out of Windows Azure. So I think it's hosted on your on-premise server, right? Then you don't need to use BasicHttpRelayBinding in your web role. You can use a normal BasicHttpBinding. Please remove any relay related bindings from your web.config.

    To set RelayClientAuthenticationType to None, please add the following configuration to your service project (not web role).

    <

     

    bindings>

    <

     

    basicHttpRelayBinding>

    <

     

    binding name="default">

    <

     

    security mode="None" relayClientAuthenticationType="None"/>

    </

     

    binding>

    </

     

    basicHttpRelayBinding>

     

     

    </bindings>


    Then make your endpoint to use the binding configuration:

    <

     

    endpoint binding="basicHttpRelayBinding" bindingConfiguration="default" .../>


    Web role does not need to perform this step. As long as RelayClientAuthenticationType is set to None on the service side, clients can connect to this service as if it is a normal WCF service.

    If you encoutered the above problem on the service side, can you confirm if you have installed .NET Services SDK? Please install the SDK. It will add some WCF extensions to the machine.config. Without SDK, you'll have to write all those extensions in the app.config. I would suggest you to install .NET Services SDK on the machine that is hosting your service.
    Lante, shanaolanxing This posting is provided "AS IS" with no warranties, and confers no rights.