Binary Serialization

Serialization can be defined as the process of storing the state of an object to a storage medium. During this process, the public and private fields of the object and the name of the class, including the assembly containing the class, are converted to a stream of bytes, which is then written to a data stream. When the object is subsequently deserialized, an exact clone of the original object is created.

When implementing a serialization mechanism in an object-oriented environment, you have to make a number of tradeoffs between ease of use and flexibility. The process can be automated to a large extent, provided you are given sufficient control over the process. For example, situations may arise where simple binary serialization is not sufficient, or there might be a specific reason to decide which fields in a class need to be serialized. The following sections examine the robust serialization mechanism provided with the .NET Framework and highlight a number of important features that allow you to customize the process to meet your needs.

Note

The state of a UTF-8 or UTF-7 encoded object is not preserved if the object is serialized and deserialized using different .NET Framework versions.

In This Section

  • Serialization Concepts
    Discusses two scenarios where serialization is useful: when persisting data to storage and when passing objects across application domains.
  • Basic Serialization
    Describes how to use the binary and SOAP formatters to serialize objects.
  • Version Tolerant Serialization
    Explains how to create serializable types that can be modified over time without causing applications to throw exceptions.

Reference

  • Remote Objects
    Describes the various communications methods available in the .NET Framework for remote communications.

Build Date: 2011-02-07