mscorlib [00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00] 1.0.5000.0 2.0.0.0 4.0.0.0 Gtk# is thread aware, but not thread safe; See the <link location="node:gtk-sharp/programming/threads">Gtk# Thread Programming</link> for details. System.Runtime.InteropServices.ComVisible(true)

Any class that might be serialized must be marked with the . If a class needs to control its serialization process, it can implement the interface. The calls the at serialization time and populates the supplied with all the data required to represent the object. The creates a with the type of the object in the graph. Objects that need to send proxies for themselves can use the and methods on to change the transmitted information.

In the case of class inheritance, it is possible to serialize a class that derives from a base class that implements . In this case, the derived class should call the base class implementation of inside its implementation of . Otherwise, the data from the base class will not be serialized.

The interface implies a constructor with the signature constructor ( information, context). At deserialization time, the current constructor is called only after the data in the has been deserialized by the formatter. In general, this constructor should be protected if the class is not sealed.

The order in which objects are deserialized cannot be guaranteed. For example, if one type references a type that has not been deserialized yet, an exception will occur. If you are creating types that have such dependencies, you can work around the problem by implementing the IDeserializationCallback interface and the OnDeserialization method.

The serialization architecture handles object types that extend the same as types that extend . These types can be marked with the and implement the interface as any other object type. Their object state will be captured and persisted onto the stream.

When these types are being used through , the remoting infrastructure provides a surrogate that preempts typical serialization and instead serializes a proxy to the . A surrogate is a helper that knows how to serialize and deserialize objects of a particular type. The proxy, invisible to the user in most cases, will be of type .

As a general design pattern, it would be unusual for a class to be both marked with the serializable attribute and extend . Developers should think carefully about the possible serialization and remoting scenarios when combining these two characteristics. One example where this might be applicable is with a . While the base class of () extends from , it is possible to capture the state of a and restore it at will. It might, therefore, be meaningful to serialize the state of this stream into a database and restore it at some later point in time. However, when used through remoting, an object of this type would be proxied.

For more information about serialization of classes that extend , see . For more information about implementing , see [<topic://cpconCustomSerialization>].

Allows an object to control its own serialization and deserialization.

- Method
  1.0.5000.0
  2.0.0.0
  4.0.0.0
  System.Void `` ``

  Any objects that are included in the are automatically tracked and serialized by the formatter.

  Code that calls requires the for providing serialization services. Associated enumeration: .

  It is not guaranteed that this method will be called only once per object instance during serialization. Therefore, the method should be implemented in such a way that its behavior will be the same regardless of the number of times it is called.

  Populates a with the data needed to serialize the target object.

  The to populate with data. The destination (see ) for this serialization.