I recently ran into a problem where .NET 2.0 clients were having
problems connecting to the enterprise .NET 3.0 WCF web services
platform that we built for internal use. We are hosting all of the web
services in IIS6 (no upgrade to IIS7 anytime in the near future) and
everything was working great for anyone running .NET 3.0 or later on
their client apps.
The root of the problem was that we had
only implemented one Endpoint, using the WSHttpBinding. This was great
for any clients running .NET 3.0 or later, but this binding doesn't
provide any backwards compatibility for clients running a framework
earlier than .NET 3.0.....
Read my full post here: http://www.schnieds.com/2008/08/multiple-wcf-endpoints-net-20-clients.html
- Aaron
http://www.churchofficeonline.com