在 XmlSerializer 与 DataContractSerializer 之间抉择

通常来说，当你想更加精确地控制生成的 XML 时，可以使用 `XmlSerializer`。如果你对生成的 XML 格式并不在意（例如所有的属性/字段均会以元素的形式保存），同时想保留对象的所有信息（包括私有属性/字段），则可以使用 `DataContractSerializer`。

参考：

• XmlSerializer vs DataContractSerializer: Serialization in Wcf
• Linq to Xml VS XmlSerializer VS DataContractSerializer

二者之间的对比简要摘录如下

XmlSerializer	DataContractSerializer
Advantages: 1. Opt-out rather than opt-in properties to serialize. This mean you don’t have to specify each and every property to serialize, only those you don’t wan to serialize 2. Full control over how a property is serialized including it it should be a node or an attribute 3. Supports more of the XSD standard	Advantages: 1. Opt-in rather than opt-out properties to serialize. This mean you specify what you want serialize 2. Because it is opt in you can serialize not only properties, but also fields. You can even serialize non-public members such as private or protected members. And you dont need a set on a property either (however without a setter you can serialize, but not deserialize) 3. Is about 10% faster than XmlSerializer to serialize the data because since you don’t have full control over how it is serialize, there is a lot that can be done to optimize the serialization/deserialization process. 4. Can understand the SerializableAttribute and know that it needs to be serialized 5. More options and control over KnownTypes
Disadvantages: 1. Can only serialize properties2. Properties must be public3. Properties must have a get and a set which can result in some awkward design4. Supports a narrower set of types5. Cannot understand the DataContractAttribute and will not serialize it unless there is a SerializableAttribute too	Disadvantages: 1. No control over how the object is serialized outside of setting the name and the order