In some applications, it is useful to know the order in which data from the various data members is sent or is expected to be received (such as the order in which data appears in the serialized XML). Sometimes it may be necessary to change this order. This topic explains the ordering rules.
Basic Rules
The basic rules for data ordering include:
-
If a data contract type is a part of an inheritance hierarchy, data members of its base types are always first in the order.
-
Next in order are the current type’s data members that do not have the Order property of the DataMemberAttribute attribute set, in alphabetical order.
-
Next are any data members that have the Order property of the DataMemberAttribute attribute set. These are ordered by the value of the Order property first and then alphabetically if there is more than one member of a certain Order value. Order values may be skipped.
Alphabetical order is established by calling the CompareOrdinal method.
Examples
Consider the following code.
[DataContract] public class BaseType { [DataMember] public string zebra; } [DataContract] public class DerivedType : BaseType { [DataMember(Order = 0)] public string bird; [DataMember(Order = 1)] public string parrot; [DataMember] public string dog; [DataMember(Order = 3)] public string antelope; [DataMember] public string cat; [DataMember(Order = 1)] public string albatross; }