Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=81995 --- shadow/81995 2007-07-03 01:24:56.000000000 -0400 +++ shadow/81995.tmp.28803 2007-07-03 01:24:56.000000000 -0400 @@ -0,0 +1,44 @@ +Bug#: 81995 +Product: Mono: Class Libraries +Version: 1.2 +OS: other +OS Details: OS Independent +Status: NEW +Resolution: +Severity: +Priority: Wishlist +Component: System +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: DATASET / DATATABLE INCORRECTLY DESERIALIZED + +Description of Problem: +Some objects, such as DataSet and DataTable, are not deserialized +correctly with BinaryFormatter or SoapBinaryFormatter. + +Steps to reproduce the problem: +1. Serialize a DataSet or DataTable object to a file or network stream. +2. Deserialized the object from the stream. + +Actual Results: +1. For DataTable, no data row deserialized (Rows.Count = 0). + No matter the object was serialized with Microsoft or MONO Formatters. +2. For DataSet, if the object was serialized with Microsoft .NET +Formatters and deserialized with MONO Formatters, an exeption occurs +(There's no 'DataSetName' element). + +Expected Results: +Since the .NET framework should be according to a unique standard and +compatible, any object serialized with any class library should be +deserialized smoothly and without any data loss. + +How often does this happen? +Every time. + +Additional Information: +The bug makes me unable to develop a server application on linux running +MONO and a client application on windows running MS .NET. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
