When custom serialization has to be taken care of, this is an essential part of the process. This is a measure and methodology used for the serialization of events, objects, graphics etc., to reduce security risks and enable the processes of communication even further. It is supported by the .NET Framework.

There are FOUR serializations in binaryformatter: (i) serializing, (just before the serialization, event raised) Apply the OnSerializing assignment, to run-method, in response to this event, (ii) serialized, Apply the OnSerialized assignment, just after, serialization, to run-method, in response, (iii) deserializing, (Apply the De-Serializing assignment, to run-method, just BEFORE deserialization takes place, and (iv) deserialized (just after deserialization).

This supports the remote procedure calls or RPC’s and interfaces to , method calls and responses, sent from the server to the client, status and response information, from called method. It is located in the namespace System.Runtime.Serialization. Formatters.Binary. Used and called on for all .Net Frameworks-based and enabled applications.

After deserialization, the high surrogate Unicode character is lost. Found in mscorlib (in mscorlib.dll)assembly.