It determines how objects are serialized, by default, IsReference=false. Setting IsReference = true allows the serialization of trees of objects that can reference each other. So with a list of Employees that each have a property for Manager (who is also an Employee), a reference to the Manager for each Employee can be held rather … Read more
If your are using DataContract serialization then you can override its default behaviour using the OnDeserialized attribute. From MSDN: When applied to a method, specifies that the method is called during deserialization of an object in an object graph. The order of deserialization relative to other objects in the graph is non-deterministic. Here is my … Read more
DataContractAttribute Class is in the System.Runtime.Serialization namespace. You should add a reference to System.Runtime.Serialization.dll. That assembly isn’t referenced by default though. To add the reference to your project you have to go to References -> Add Reference in the Solution Explorer and add an assembly reference manually.
Your “server-side” class won’t be “made available” to the client, really. What happens is this: based on the data contract, the client will create a new separate class from the XML schema of the service. It cannot use the server-side class per se! It will re-create a new class from the XML schema definition, but … Read more
You can do this with the DataContractSerializer – the answer is to take over the Xml serialization yourself by implementing the IXmlSerializable interface. For write-only support – you can leave the implementation of ReadXml empty, and return null for GetSchema, and then write the implementation of WriteXml as follows: public class MyPerson : IXmlSerializable { … Read more
Simply use Json.Net’s OptOut attribute. It will take precedence over DataContract. [DataContract] [JsonObject(MemberSerialization.OptOut)]
This can be achieved, but you will have to override the default serializer by applying the [XmlSerializerFormat] attribute to the DataContract. Although it can be done, this does not perform as well as the default serializer, so use it with caution. The following class structure will give you the result you are after: using … … Read more
Since a lot of programmers were overwhelmed with the [DataContract] and [DataMember] attributes, with .NET 3.5 SP1, Microsoft made the data contract serializer handle all classes – even without any of those attributes – much like the old XML serializer. So as of .NET 3.5 SP1, you don’t have to add data contract or data … Read more