I noticed that DataContractSerializer is using serialization in alphabetical order. If you do not follow the below rules you will end up missing data after deserialization of your XML.

    [Serializable, DataContract(Namespace = "your-namespace")]

    public class YourObject : DataModelDeserializable<YourObject>

    {

        [DataMember]

        public string PostalCode { get; set; }

        [DataMember]

        public string City { get; set; }

        [DataMember]

        public DateTime Street { get; set; }

    }

If you would serialize the above the XML would be in alphabetical order;

<City>New York</City>

<PostalCode>23001</PostalCode>

<Street>1st Avenue</Street>

If you would now create your XML from another component, intending to use it with the deserialize process you might mistake the alphabetical order;

<Street>1st Avenue</Street>

<PostalCode>23001</PostalCode>

<City>New York</City>

You will not notice that the properties are not filled with any values from the elements in the XML. The reason for this is the alphabetical processing. You might even discover that only some properties are correct because you start with having some in the right alphabetical order but fail with the rest of the XML and the equivalent properties.

You can solve this in 2 ways;

1. Make sure that the XML file elements are in alphabetical order.

2. The first might fail because you are limited to control the element order so the you can instruct DataContractSerializer that it should order its serialization differently.

    [Serializable, DataContract(Namespace = "your-namespace")]

    public class YourObject : DataModelDeserializable<YourObject>

    {

        [DataMember(Order=2)]

        public string PostalCode { get; set; }

        [DataMember(Order=3)]

        public string City { get; set; }

        [DataMember(Order=1)]

        public DateTime Street { get; set; }

    }

/* now the serialization process is done in order Street, PostalCode, City */