Bug 59178 - XmlSerializer not compatible with .NET
Summary: XmlSerializer not compatible with .NET
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.XML ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: Future Release
Assignee: Bugzilla
Depends on:
Reported: 2017-09-01 14:20 UTC by jeroen.bernsen
Modified: 2017-09-11 10:42 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Solution to reproduce (301.86 KB, application/x-zip-compressed)
2017-09-01 14:20 UTC, jeroen.bernsen

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 59178 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description jeroen.bernsen 2017-09-01 14:20:48 UTC
Created attachment 24524 [details]
Solution to reproduce

I included a simplified solution with XML Deserialization unit tests that succeed on UWP but fail on Android and iOS.

It seems that if there are [XmlElementAttribute(Order = 0)] attributes on both base and derived classes that the order is interpreted different on Mono vs .NET. This is especially a problem since we have large generated files with types for Serialization.

So the order is different for serialization and deserialization