Occurs when an exception is serialized to create an exception state object that contains serialized data about the exception.
Assembly: mscorlib (in mscorlib.dll)
The exception state object implements the ISafeSerializationData interface.
When the event is subscribed to, the exception is deserialized and created as an empty exception. The exception's constructor is not run, and the exception state is also deserialized. The CompleteDeserialization callback method of the exception state object is then notified so that it can push deserialized data into the empty exception.
The event enables transparent exception types to serialize and deserialize exception data. Transparent code can execute commands within the bounds of the permission set it is operating within, but cannot execute, call, derive from, or contain critical code.
If the event is not subscribed to, deserialization occurs as usual using the Exception constructor.
Typically, a handler for the event is added in the exception's constructor to provide for its serialization. But because the constructor is not executed when the event handler executes, serializing a deserialized exception can throw a SerializationException exception when you try to deserialize the exception. To avoid this, you should also add the handler for the event in the ISafeSerializationData::CompleteDeserialization method. See the Examples section for an illustration.Notes to Implementers
If this event is subscribed to and used, all derived types that follow in the inheritance hierarchy must implement the same serialization mechanism.
The following example defines a BadDivisionException that handles the event. It also contains a state object, which is a nested structure named BadDivisionExceptionState that implements the ISafeSerializationData interface.
The BadDivisionException exception is thrown when a floating-point division by zero occurs. During the first division by zero, the example instantiates a BadDivisionException object, serializes it, and throws the exception. When subsequent divisions by zero occur, the example deserializes the previously serialized object, reserializes it, and throws the exception. To provide for object serialization, deserialization, reserialization, and deserialization, the example adds the event handler both in the BadDivisionException class constructor and in the ISafeSerializationData::CompleteDeserialization implementation.
Windows Phone 8.1, Windows Phone 8, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.