Re: DataSet and serialization is dangerous

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: ABad (anonymous_at_discussions.microsoft.com)
Date: 02/02/05 

Date: Tue, 1 Feb 2005 20:22:23 -0500

You may have to look deeper into the different serialization/deserialization
techniques and the options with each one, and how their round-trip usage
produces results that may differ with the original in-memory representation.

Using the technique you have shown the resulting XML file has the previous
version with only the father, but it also has the new dataset version with
the father and child relationship. So the data isn't lost, but the
serialization and deserialization technique you have chosen may cause
different in-memory representations than the original dataset. Looking at
the GUI results thats my guess on what is happening. The read dataset is
showing only the previous version while the original is showing the new
dataset version.

If you change your serialization/deserialization technique to:
    - dsOriginal.WriteXml("myFileName.xml",XmlWriteMode.WriteSchema)
    - dsRead = new Dataset
    - dsRead.ReadXML("myFileName.xml",XmlReadMode.Auto)

You get the results you expect. This shows this
serialization/deserialization technique produces what the original dataset
had in-memory.

Just an observation.

- ABad