Bug 11822 - XmlSerialization '\t' character prior to mono 3 differs from .net
Summary: XmlSerialization '\t' character prior to mono 3 differs from .net
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.XML ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-04-17 08:13 UTC by moljac
Modified: 2015-03-17 06:40 UTC (History)
3 users (show)

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

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 on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description moljac 2013-04-17 08:13:37 UTC
During port of SharpSerializer differences in XmlSerialization for serializing char '\t' noticed.

In versions 3.0+ difference is not noticed.

complete solution: https://github.com/moljac/MonoVersalSharpSerializer

reduced sample (console): https://github.com/moljac/MonoVersalSharpSerializer/tree/master/HelloWorldApp.Console.BugXmlSerializationInMono

some description on forum:

http://forums.xamarin.com/discussion/3243/sharpserializer-port-xmlserialization-bug-in-mono-3-0
Comment 1 Atsushi Eno 2015-03-17 06:40:03 UTC
Looks like it is "bug" (if it was) in 2.10.x and not for 3.0.