input: [Category] Data Contracts [Description] When generating an equivalent data contract to an already existing one, it is insufficient to alias the type and the members. You also need to ensure that the order of serialization is maintained – first by class hierarchy then alphabetically. In case of a discrepancy, you can compensate by setting the Order property of the DataMember attribute as shown in the download. [Last Updated] 9/7/2006 [Title] 
output: Order and Equivalence