Microsoft Developer Network > Página principal de foros > Windows Azure > Configuration binding extension could not be found
Formular una preguntaFormular una pregunta
 

RespondidaConfiguration binding extension could not be found

Respuestas

  • viernes, 03 de julio de 2009 7:06Yi-Lun LuoMSFT, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    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.

Todas las respuestas

  • viernes, 03 de julio de 2009 7:06Yi-Lun LuoMSFT, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    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.