Deserialize bug 2.0.0-alpha6

Imagine the following class:

public class Person
{
    public string FirstName { get; set; }

    public string LastName { get; set; }

    public string Nationality { get; set; }

    public bool Married { get; set; }
}

When serializing the following Person …

var person = new Person{ FirstName = "John", LastName = "Doe" };
serializer.Serialize(person);

The following XML is generated (more or less):

<Person>
    <FirstName>John</FirstName>
    <LastName>Doe</LastName>
    <Married>false</Married>
</Person>

And everything is OK with the world, deserializing works properly too etc etc.

But now imagine this scenario:

var person = new Person{ FirstName = "John", LastName = string.Empty, Nationality = "British", Married = true };
serializer.Serialize(person);

This will produce the following XML:

<Person>
    <FirstName>John</FirstName>
    <LastName></LastName>
    <Nationality>British</Nationality>
    <Married>true</Married>
</Person>

Which also looks exactly what it should like. However when I try to deserialize that… I end up with a Person where LastName == string.Empty, Nationality == null and Married == false

[Mike-E-angelo]

OK this was due to how we’re using the native XmlReader and extracting the value from that. I have checked in a fix. @wojtpl2 I noticed we haven’t pushed Alpha 7 yet. Were we supposed to? I forget. 😆 Last I remember I was going to work on v2.0 documentation, which I hope to start up tomorrow and have done next week.

I am thinking we should get this fix in with an Alpha 7 push when you find the time. 👍

[Mike-E-angelo]

This has been fixed in the latest versions. Please feel free to comment on this issue (or open another issue) if there is any outstanding/expected work if not. Thanks again for your participation, @FaustoNascimento!