Thank you Steve. This is

Mark Eilenberger — Sun, 06 Sep 2009 19:57:53 -0400

Thank you Steve.

This is very helpful.

I'm looking for a solution where the service can be both a NetDataContract and a DataContract simultaneously. This way, if someone creates a proxy and wants to use it as a mechanism to return a concrete object because they are not a .Net client, then it works. Maybe the ServiceKnownType is good for this. Using example 1, I can code to interfaces inside my WCF classes but always render out a concrete implementation vs. an interface.

However, some of my consumers will be .Net. In fact the .Net consumers are in-house developers that insist on passing and returning interfaces. I can have them use my application tier (which would look like example 2), or I can have them use my web tier (example 1). But my web tier does schema validation and versioning, etc. and I would prefer that everyone use the web tier.

The example you provided doesn't have DataMember or DataContract attributes. I need those so proxy generators can infer a schema and talk SOAP. But I'd like my in-house guys to be able to create a channel and use .Net serialization.

Do you think this is possible?

Using Interfaces as Parameters (Part 2)

Steve Seymour — Sun, 03 Dec 2006 00:00:00 -0500

Ahhh...and now I've found what I was looking for. Thanks to Avner Kashtan's Blog, which pointed me to Aaron Skonnard's blog...

ThoughtShapes - Using Interfaces as Parameters (Part 2) - Comments

Thank you Steve. This is

Using Interfaces as Parameters (Part 2)