What is the difference between datacontractserializer and xmlserializer

AreEqual employeeObj. NewGuid ; employee. NewGuid ; education. EmployeeId; education. NewGuid ; educationObj2. EmployeeId; educationObj2.

Add educationObj2 ; employee. Find the source code and full project. It is attached. View All. Habibur Rony Updated date Nov 24, Coverage Topic. The problem can be solved in many different ways. I have used the following references in the project for the XML and data-contract serialization:. There is no doubt that these codes are okay. Look at the above image, I have used the using block and these are not the major change in this implementation.

Look at the above image; I have changed very silly things. Look at the above codes, it is almost similar to the previous implementation except for DataContractSerializer Class. Again, if you look at the model class of the employee, then you will see that, at runtime, it is alphabetically ordered. Look at the above codes, I have wrapped the previous implementation of the DataContractSerializerUtility class. Now if I run the following test, then it will be passed the test. DataContractSerializer does not need any default constructor before serializing any type.

DataContractSerializer does not give more control over the generated xml structure compared to the XmlSerializer. DataContractSerializer can able to serialize types that implements Idictionary. We can serialize a type that marked with [Serializable] attribute with DataContractSerializer. It serializes all the members private, public even they are marked with [XmlIgnore]. XmlSerializer uses opts-out approach i. This is called as opts-out approach.

XmlSerializer can serialize only public types. Once again I had this discussion at work. Why use one of them over the other? The two serializers are very different and tackle XML serialization in their own ways. XML serialization has not seen much love from Microsoft over the last many years. Net for example. The same global element declaration rules apply to legacy dataset types.

Note that the XmlRootAttribute cannot override global element declarations added through custom code, either added to the XmlSchemaSet using the schema provider method or through GetSchema for legacy dataset types.

IXmlSerializable element types have either the IsAny property set to true or have their schema provider method return null. Serializing and deserializing an element type is very similar to serializing and deserializing a content type. However, there are some important differences:. The WriteXml implementation is expected to write exactly one element which could of course contain multiple child elements.

It should not be writing attributes outside of this single element, multiple sibling elements or mixed content. The element may be empty. The ReadXml implementation should not read the wrapper element. It is expected to read the one element that WriteXml produces. When serializing an element type regularly for example, as a data member in a data contract , the serializer outputs a wrapper element before calling WriteXml , as with content types.

However, when serializing an element type at the top level, the serializer does not normally output a wrapper element at all around the element that WriteXml writes, unless a root name and namespace are explicitly specified when constructing the serializer in the DataContractSerializer or NetDataContractSerializer constructors.

For more information, see Serialization and Deserialization. When serializing an element type at the top level without specifying the root name and namespace at construction time, WriteStartObject and WriteEndObject essentially do nothing and WriteObjectContent calls WriteXml. In this mode, the object being serialized cannot be null and cannot be polymorphically assigned. Also, object graph preservation cannot enabled and the NetDataContractSerializer cannot be used. When deserializing an element type at the top level without specifying the root name and namespace at construction time, IsStartObject returns true if it can find the start of any element.

ReadObject with the verifyObjectName parameter set to true behaves in the same way as IsStartObject before actually reading the object. ReadObject then passes control to ReadXml method. The schema exported for element types is the same as for the XmlElement type as described in an earlier section, except that the schema provider method can add any additional schema to the XmlSchemaSet as with content types.

Using the XmlRootAttribute attribute with element types is not allowed, and global element declarations are never emitted for these types. However, there are some differences in how these are treated in the data contract model. The important differences are summarized in the following list:. The schema provider method must be public to be used in the XmlSerializer , but does not have to be public to be used in the data contract model.

The schema provider method is called when IsAny is true in the data contract model but not with the XmlSerializer. When the XmlRootAttribute attribute is not present for content or legacy dataset types, the XmlSerializer exports a global element declaration in the blank namespace.

In the data contract model, the namespace used is normally the data contract namespace as described earlier. Be aware of these differences when creating types that are used with both serialization technologies.

When importing a schema generated from IXmlSerializable types, there are a few possibilities:. The generated schema may be a valid data contract schema as described in Data Contract Schema Reference. In this case, schema can be imported as usual and regular data contract types are generated.

The generated schema may not be a valid data contract schema. For example, your schema provider method may generate schema that involves XML attributes that are not supported in the data contract model. In this case, you can import the schema as IXmlSerializable types. This is described in detail in the Importing Schema to Generate Classes.

Note that you must work directly with the XML for your type instances. You may also consider using a different serialization technology that supports a wider range of schema — see the topic on using the XmlSerializer. You may want to reuse your existing IXmlSerializable types in the proxy instead of generating new ones. In this case, the referenced types feature described in the Importing Schema to Generate Types topic can be used to indicate the type to reuse.

In the.