(De)serialization of objects with property-name same as object-name stopped working correctly since V3.2

Given the classes

public class Person
{
    public string LastName { get; set; } = string.Empty;
    public string FirstName { get; set; } = string.Empty;
    public string Salutation { get; set; } = string.Empty;
}
public class Item
{
    public string Description { get; set; } = string.Empty;
    public string Person { get; set; } = string.Empty;
    public byte[] Content { get; set; }
}

the code

var item = new Item();
item.Person = "Testperson";
item.Description = "Testing ExtendedXmlSerializer";
item.Content = new byte[] { 12, 13, 14, 15, 16 };

string content = serializer.Serialize(new XmlWriterSettings { Indent = true }, item);

var deserializedItem = serializer.Deserialize<Item>(new XmlReaderSettings(), content);

results in deserializedItem.Person being string.Empty and deserializedItem.Content being null

The resulting xml after serialization looks like

<?xml version="1.0" encoding="utf-8"?>
<Item xmlns="clr-namespace:TestingRetryItem;assembly=TestingRetryItem">
  <Description>Testing ExtendedXmlSerializer</Description>
  <Person xmlns:exs="https://extendedxmlserializer.github.io/v2" exs:member="">Testperson</Person>
  <Content>DA0ODxA=</Content>
</Item>

The problem here seems to be exs:member="" because after manually deleting this from the resulting xml the deserialization works. There is no exception thrown neither at serialization nor deserialization. The order of the properties is relevant as well, because e.g having the Item class look like

public class Item
{
    public string Description { get; set; } = string.Empty;
    public byte[] Content { get; set; }
    public string Person { get; set; } = string.Empty;
}

the Content property isn’t null anymore. It just seems that after accessing a property with a name equal to a class-name the deserialization stops without throwing an exception.

[Heslacher]

You don’t need to apologize. I have fixed the issue by using EnableReferences() for serialization and omitting it for deserialization. I have tested it and it works. Thanks again for your help and this wonderful project.

[Mike-E-angelo]

Thank you very much! I appreciate that. I definitely feel beholden to this project and all the developers that depend on it, so when things don’t work I take that responsibility seriously.

I like your other solution as well. I didn’t even think of that, and hopefully, if someone in the future runs into this problem they have a couple of workarounds they can possibly implement.

Anyways, thank you for your understanding and kind words. You made my day. 🙏 Closing for now.