Using WCF for project where client doesn't have .NET3.0 (WinFX)

The title pretty much says it! We really like the WCF and would like to use
it in an upcoming project. However we can't justify distributing the .NET3.0
Framework at this stage to our client.

Is there any way that WCF can run from out end and the client can still
communicate using ASMX. In other words, can the two technologies be used
together?

On the WCF side provide an endpoint that uses the "basicHttpBinding". This
binding will permit a client to communicate with a WCF service as if it were
ASMx.

--
Chris Rolon
Principal Consultant
Neudesic

This posting is provided "AS IS" with no warranties, and confers no rights.



"Matt Swift" wrote:

> The title pretty much says it! We really like the WCF and would like to use
> it in an upcoming project. However we can't justify distributing the .NET3.0
> Framework at this stage to our client.
>
> Is there any way that WCF can run from out end and the client can still
> communicate using ASMX. In other words, can the two technologies be used
> together?

Look at http://windowssdk.msdn.microsoft.com.../ms751433.aspx
Arkady

"Matt Swift" <MattSwift@discussions.microsoft.com> wrote in message
news6F2565B-32E4-4B5F-BF96-73DD96D53C42@microsoft.com...
> The title pretty much says it! We really like the WCF and would like to
> use
> it in an upcoming project. However we can't justify distributing the
> .NET3.0
> Framework at this stage to our client.
>
> Is there any way that WCF can run from out end and the client can still
> communicate using ASMX. In other words, can the two technologies be used
> together?

July 12, 2006

Well, if you mean web services when you mentioned ASMX.... web services
communicate using soap/xml, and therefore have great interop-abilities.

If you can create the web service in 3.0 and still have the SOAP readable
from .Net 2.0 components (basically an interop issue), then I don't see any
reason why you can't use Indigo on your end and other versions on the client
side (granted, the client side would have to be written in .Net 2.0 or
earlier and not 3.0).

You could always create a very simple test web service in 3.0, and try to
interop with it using .Net 2.0 as a pilot program on your side.... doesn't
need the client to do anything to see if it would work on a simple level.

Hope this helps and good luck!
--
Joseph Bittman
Microsoft Certified Solution Developer
Microsoft Most Valuable Professional -- DPM

Web Site/Blog: http://CactiDevelopers.ResDev.Net/

"Matt Swift" <MattSwift@discussions.microsoft.com> wrote in message
news6F2565B-32E4-4B5F-BF96-73DD96D53C42@microsoft.com...
> The title pretty much says it! We really like the WCF and would like to
> use
> it in an upcoming project. However we can't justify distributing the
> .NET3.0
> Framework at this stage to our client.
>
> Is there any way that WCF can run from out end and the client can still
> communicate using ASMX. In other words, can the two technologies be used
> together?