Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Quick Tip: Debug XmlSerializer Errors

DZone's Guide to

Quick Tip: Debug XmlSerializer Errors

Serialization and deserialization can be a bit of a black box. We look at how to find out what's happening during the serialization/deserialization process.

· Web Dev Zone ·
Free Resource

Learn how Crafter’s Git-based content management system is reinventing modern digital experiences. Download this white paper now. 

One of the hardest things to detect is whether serialization or deserialization is working when you use XmlSerializer or a DataContractSerializer.

In my Serialization/Deserialization Series, I use the XmlSerializer and found it made life a little easier.

However, there are times when you want to use an XmlSerializer over a DataContractSerializer. Here are some of the differences:

DataContractSerializer

  • It's faster than XmlSerializer (10% to be technical about it).
  • Used specifically for WCF services to serialize/deserialize to/from JSON or XML.
  • Serializes properties and fields (IMPORTANT: if it's XML, they MUST be in alphabetical order).

XmlSerializer

  • Only used for serializing/deserializing XML.
  • Allows for customizable serializing.
  • Only public properties are serialized.

The reason I bring these differences up is that XmlSerializer is a little more customizable, allowing you more flexibility when serializing or deserializing your objects.

You can add XML attributes to your code by making a property an attribute or element, whereas DataContractSerializer is a little bit harder to control.

Opening the Black Box

Way back in 2005, there wasn't a DataContractSerializer, so for our specific project, we had to use an XmlSerializer.

I recently experienced difficulties understanding why some objects in my code weren't deserializing and forgot how to check to see what was happening under the hood.

The XmlSerializer class has events detailing the deserialization process as it reads your XML.

These events occur when the serializer can't determine how to deserialize the object based on the XML you feed it.

Is it a problem with an Attribute, Node, Element, or Unreferenced Object?

var serializer = new XmlSerializer(typeof(Vendor));
serializer.UnknownAttribute += (sender, args) =>
{
    System.Xml.XmlAttribute attr = args.Attr;
    Console.WriteLine($"Unknown attribute {attr.Name}=\'{attr.Value}\'");
};
serializer.UnknownNode += (sender, args) =>
{
    Console.WriteLine($"Unknown Node:{args.Name}\t{args.Text}");
};
serializer.UnknownElement += 
    (sender, args) => 
        Console.WriteLine("Unknown Element:" 
            + args.Element.Name + "\t" + args.Element.InnerXml);
serializer.UnreferencedObject += 
    (sender, args) => 
        Console.WriteLine("Unreferenced Object:"
            + args.UnreferencedId + "\t" + args.UnreferencedObject.ToString());

Of course, you execute this before you perform your deserialization.

Conclusion

The team I work with have wrestled with some XmlSerializer and DataContractSerializer issues in the past and these events provided some clues on how to better structure your XML.

I'm pretty sure there are also some legacy applications out there still using XmlSerializers, so I thought this would be a great quick tip on debugging XML through an XmlSerializer.

How do you debug your XmlSerializer errors? Do you still use XmlSerializer? Are you using DataContractSerializer? Post your tips below and let's discuss.

Crafter CMS is a modern Git-based platform for building innovative websites and content-rich digital experiences. Download this white paper now.

Topics:
deserialization ,xml ,web dev ,debugging

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}