Using data contract solves the issue. It was due to that (1) it was not picking base type members in ISerializable, so do not use ISerializable (e.g. use data contract), and (2) fields with special members were not encoded in valid xml name, which happens only to automatically generated fields for auto properties.
For the fix details, see (1) http://github.com/mono/mono/commit/c893d9c638f9b2e86c71779165d508fddfc875a3 (2) http://github.com/mono/mono/commit/57c4337d79ace6f27903b2f896806263a71870bf mono 2.8 is rumored to be released soon, but it won't include this specific fix (the branching was done earlier last week). In current plan, 2.8.2 will include it (as it will be branched from git head), but I can't say the release plan is stable yet. Atsushi Eno On 2010/08/29 22:55, SuperCiccio wrote: > Thanks for your attention. > Are there any workaround? > Or, when will a version be avaiable? > > Cheers _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list