# V3104. The 'GetObjectData' implementation in unsealed type is not virtual, incorrect serialization of derived type is possible.

The analyzer detected an unsealed class implementing the 'ISerializable' interface but lacking virtual method 'GetObjectData'. As a result, serialization errors are possible in derived classes.

Consider the following example. Suppose we have declared a base class and a class inheriting from it as follows:

    [Serializable]
    class Base : ISerializable
    {
      ....
      public void GetObjectData(SerializationInfo info,
                                StreamingContext context)
      {
        ....
      }
    }

    [Serializable]
    sealed class Derived : Base
    {
      ....
      public new void GetObjectData(SerializationInfo info,
                                    StreamingContext context)
      {
        ....
      }
    }

There is also the following code to manage object serialization:

    void Foo(BinaryFormatter bf, MemoryStream ms)
    {
      Base obj = new Derived();
      bf.Serialize(ms, obj);
      ms.Position = 0;
      Derived derObj = (Derived)bf.Deserialize(ms);
    }

The object will be serialized incorrectly because the 'GetObjectData' method will be called from the base class, not the derived one. Therefore, the members of the derived class will not be serialized. Attempting to retrieve the values of the members added by method 'GetObjectData' of the derived class when deserializing the 'SerializationInfo' object will cause raising an exception because there are no such values in the object.

To fix this error, the 'GetObjectData' method must be declared as 'virtual' in the base class, and as 'override' in the derived one. The fixed code will then look like this:

    [Serializable]
    class Base : ISerializable
    {
      ....
      public virtual void GetObjectData(SerializationInfo info,
                                        StreamingContext context)
      {
        ....
      }
    }

    [Serializable]
    sealed class Derived : Base
    {
      ....
      public override void GetObjectData(SerializationInfo info,
                                         StreamingContext context)
      {
        ....
      }
    }

If the class contains only an explicit implementation of the interface, an implicit implementation of virtual method 'GetObjectData' is also required. Consider the following example. Suppose we have declared the classes as follows:

    [Serializable]
    class Base : ISerializable
    {
      ....
      void ISerializable.GetObjectData(SerializationInfo info,
                                       StreamingContext context)
      {
        ....
      }
    }

    [Serializable]
    sealed class Derived : Base, ISerializable
    {
      ....
      public void GetObjectData(SerializationInfo info,
                                StreamingContext context)
      {
        ....
      }
    }

You cannot call to the 'GetObjectData' method of the base class from the derived class. Therefore, some of the members will not be serialized. To fix the error, virtual method 'GetObjectData' must be implicitly implemented in addition to the explicit interface implementation. The fixed code will then look like this:

    [Serializable]
    class Base : ISerializable
    {
      ....
      void ISerializable.GetObjectData(SerializationInfo info,
                                        StreamingContext context)
      {
        GetObjectData(info, context);
      }

      public virtual void GetObjectData(SerializationInfo info,
                                        StreamingContext context)
      {
        ....
      }
    }

    [Serializable]
    sealed class Derived : Base
    {
      ....
      public override void GetObjectData(SerializationInfo info,
                                         StreamingContext context)
      {
        ....
        base.GetObjectData(info, context);
      }
    }

If the class is not expected to have any descendants, declare it as 'sealed'.