Why are two different processes to configure the serialization and to map the object ?
Even if sometime they may appear similar or an overhead, they represent two completely different processes. Serialization is the process of converting your object in a data content, independent from every data source like Xml or a database. In other words serialization tells which members, with which name and type are data content. Mapping is the process of associating serialized data with database tables and fields, depending on your schema and database rules. For example if you map your objects to Xml or an Access database for offline data elaboration and an Oracle or Sql server database for online data transactions, you should use the same serialization configuration but probably a different mapping. You can also map your objects to completely different database schemas, but the serialization should be the same. DADO Database Mapper provides different serialization surrogates, for example one serializing all public members (properties and fields), one working only on the fields (pub
