Home/ Questions/Q 128889
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T05:42:24+00:00

We wish to use the Binary Formatter. In debugging, thus far, it seems that

  • 0

We wish to use the Binary Formatter. In debugging, thus far, it seems that it does not execute the getters for public properties. Does the XML Serializer behave the same way? Also, during deserialization, will the deserializers use the setters to apply the values during deserialization?

Thus far, our testing with BinaryFormatter shows that it simply writes directly to and from member variables. It does not step through any of the getters or setters. Is the XML Serializer the same way?

What if a public property did something silly like Random().Next? Will this be serialized by the Binary Formatter? It seems that with the XML Serializer, you would need to decorate this member appropriately to get it to participate. The Binary Formatter seems to only work, again, on member variables.

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Think about it this way:

    Let’s say you’re deserializing a class with several serialized properties, and the setter for the last property has side effects that can alter the values of another property. The altered property no longer reflects your serialized data. Do you really want it to use that setter?

    On the other hand, what if there is no backing store for a property? Perhaps it’s a composite property allowing you to get and set values of all the others at once. Arguably this property shouldn’t be serialized (or only this property should be serialized, depending on how things work), but there could be other examples. How does the formatter know where to assign the value for such a property?

    So which is it? I had to look it up and couldn’t quickly find an authoritative source, but it looks like the XmlSerializer does use getters and setters while the BinaryFormatter does not use getters or setters.

    And that kind of makes sense. My first point showed that you don’t really want to use getter/setters. My 2nd point showed that you may have to use them. The binary formatter can just take the exact in-memory representation of the object, so it skips the getter/setters. The XmlSerializer, which doesn’t have this ability, has to use the other method.

    You should probably set up a quick test project for yourself so you can see it in action.

    • 0