This project is read-only.

Q. Will DotSerialize work with a class containing only auto-properties since it serializes only fields by default?

A. Yes, DotSerialize will work without problems and without requiring any changes. Classes with auto-properties actually still create hidden backing fields and DotSerialize will see and use these out of the box. It will however use the name of the auto-property instead of the automatic backing field for the xml element names. This results in a more user readable xml output.

Q. Does DotSerialize require a pubilc constructor on my classes to deserialize them?

A. No.

Q. Does DotSerialize require a parameterless constructor on my classes to deserialize them?

A. No, it does not. DotSerialize makes an intelligent attempt to figure out the best constructor to use on your class and uses it to create an instance.

Q. Do I need to decorate my classes with special attributes for DotSerialize to handle any issues of polymorphism?

A. No, DotSerialize will automatically recognize all your data types, regardless of the type of the field they are stored in. DotSerialize will serialize/deserialize your types by itself without requiring help.

Q. Do I need to decorate my classes with special attributes to customize the xml output from DotSerialize?

A. No, though controlling layout via attribute decoration is offered and is the simplest way to customize layout. If you cannot decorate a class with attributes you can still customize the resulting xml by means of a custom xml class map or by creating a custom type serializer. Both of these approaches are discussed in detail in the Documentation.

Q. Can I customize the Xml that DotSerialize outputs?

A. Yes, take a look at the Basic Customization and Advanced Customization documentation topics to learn more on how you can do this.

Last edited Mar 9, 2015 at 1:43 AM by WiredWiz, version 13