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 CompleteDeserialization callback method of the exception state object is then notified so that it can push deserialized data into the empty exception.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
Theevent 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 Exception constructor.event is not subscribed to, deserialization occurs as usual using the
Typically, a handler for the 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.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
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.
Available since 4.0