Can I expose the same interface with two different binding without changing code?

I have a working WCF service with wsHttpBinding. I want to .Net Framework
1.1 clients to see it at ASMX and therefore need basicHttpBinding.

It is pretty easy to expose a service as ASMX:

<service name="MyName" behaviorConfiguration="AsxmBehavior">
<endpoint address=""
binding="basicHttpBinding"
contract="IMyService" />
</service>

<behavior name="AsxmBehavior">
<serviceMetadata httpGetEnabled="True"/>
<serviceDebug includeExceptionDetailInFaults="False" />
</behavior>

However, I would like both WCF and ASMX services running at the same time
without changing any code (addding new classes or interfaces)

Is it possible?

-Stan

Yes.

You should be able to do it by simply adding another endpoint. Of course
the address URL should reflect the protocol you want to use. net.tcp://
or net.msmq:// etc.

Cheers,
--
Naraendirakumar R.R
Software Architect


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

"StanB" <stan@community.nospam.com> wrote in message
news:%23sZa54CuHHA.768@TK2MSFTNGP04.phx.gbl...
>I have a working WCF service with wsHttpBinding. I want to .Net Framework
>1.1 clients to see it at ASMX and therefore need basicHttpBinding.
>
> It is pretty easy to expose a service as ASMX:
>
> <service name="MyName" behaviorConfiguration="AsxmBehavior">
> <endpoint address=""
> binding="basicHttpBinding"
> contract="IMyService" />
> </service>
>
> <behavior name="AsxmBehavior">
> <serviceMetadata httpGetEnabled="True"/>
> <serviceDebug includeExceptionDetailInFaults="False" />
> </behavior>
>
> However, I would like both WCF and ASMX services running at the same time
> without changing any code (addding new classes or interfaces)
>
> Is it possible?
>
> -Stan
>
>

I know I should be able just to add an endpoint - in theory.

Do you have a working example of configuration?


"Naraendirakumar R.R." <nospam@nospam.com> wrote in message
news:eyIP$DcvHHA.4736@TK2MSFTNGP05.phx.gbl...
> Yes.
>
> You should be able to do it by simply adding another endpoint. Of
> course the address URL should reflect the protocol you want to use.
> net.tcp:// or net.msmq:// etc.
>
> Cheers,
> --
> Naraendirakumar R.R
> Software Architect
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> "StanB" <stan@community.nospam.com> wrote in message
> news:%23sZa54CuHHA.768@TK2MSFTNGP04.phx.gbl...
>>I have a working WCF service with wsHttpBinding. I want to .Net Framework
>>1.1 clients to see it at ASMX and therefore need basicHttpBinding.
>>
>> It is pretty easy to expose a service as ASMX:
>>
>> <service name="MyName" behaviorConfiguration="AsxmBehavior">
>> <endpoint address=""
>> binding="basicHttpBinding"
>> contract="IMyService" />
>> </service>
>>
>> <behavior name="AsxmBehavior">
>> <serviceMetadata httpGetEnabled="True"/>
>> <serviceDebug includeExceptionDetailInFaults="False" />
>> </behavior>
>>
>> However, I would like both WCF and ASMX services running at the same time
>> without changing any code (addding new classes or interfaces)
>>
>> Is it possible?
>>
>> -Stan
>>
>>
>
>

Yeah. All just set another address for the new endpoint. Nothing
special.