I have a case where I need to transfer large amounts of serialized object graphs (via NetDataContractSerializer) using WCF using wsHttp. I\'m using message security and woul
Some lighter, but not guaranteed solutions, would be to
DataContractSerializer instead since you own both sides. This does not require embedded type information, which is significantly large.[DataMember(EmitDefaultValue = false)] which is discussed in a question I asked - again because you own both sides; doing so will cut down some on the message size (how much depends of course on how many fields in the graph are defaults).[DataContract(IsReference=true)], especially if you have many repeated value objects or reference data These are, of course trade-offs, for example with readability.