How to change the order of Deserialization using BinaryFormatter in C#?

Lets say I have classA which contains classB and both are [Serializable].

I assumed, that on Deserialization classB would be deserialized first.

This is not the case however, as I could confirm by just logging when each [OnDeserialized] methods were hit.

Now I ha开发者_如何学编程ve the following issue:

After classA's deserialization is complete, it is supposed to set itself up, using values from classB. Unfortunately, classB has not been deserialized yet at this point, so classA gets set up wrong.

My problem would be solved, if I could force the BinaryFormatter to deserialize classB before classA, or resolve the Object Graph bottom to top instead of top to bottom.

Another obvious solution would be to make classB fire an event when it is deserialized and then have classA set itself up, but I want to stay away from this non-elegant workaround.

So I would appreciate if somebody knows of a better solution.

If you have to have explicit control over the order of your objects serialization and deserialization, I suggest you implement the ISerializable interface for A:

public class ClassA : ISerializable
{
    private ClassB _dependency;

    public ClassA(SerializationInfo information, StreamingContext context)
    {
        _dependency 
            = (ClassB)information.GetValue("_dependency", typeof(ClassB));

        // TODO: Get other values from the serialization info.
        // TODO: Set up stuff from dependent object.
    }

    public SerializationInfo GetObjectData()
    {
        information.AddValue("_dependency", _dependency, typeof(ClassB));

        // TODO: Add other fields to the serialization info.
    }
}

I would suggest to just used a method marked with [OnDeserialized] to handle any post-serialization initialization you require and not concern yourself with the order in which they are deserialized.

You could make classA implement the IDeserializationCallback interface. Its OnDeserialization method will only be called once the entire object graph has been deserialized, including the classB object.

These two steps might do the trick:

1. Make the [OnDeserialized] method of classB safe to call multiple times.
2. In the [OnDeserialized] method of classA, explicitly call the [OnDeserialized] method on the contained classB object.

The BinaryFormatter will end up calling the [OnDeserialized] method on the classB object again, but step 1 makes that safe.