Skip to main content

Custom Object Serialization in .Net



Namespace: System.Runtime.Serialization

In a very complex object creation scenario we may want to implement serialization our self. To do custom serialization one must apply the serialization attributes to the class in the same way and also class must implement ISerializable interface.

Constructor to be implemented should look like:
Protected <ClassName>(SerializationInfo si, StreamingContext sc)
{
                productid = info.GetInt32(“Product ID”);
                productprice = info.GetInt32(“Price”);
productQuantity = info.GetInt32(“Quantity”);
total = productprice * productQuantity;
}

For Deserialization implement the method:

[SecurityPermissionAttribute(SecurityAction.Demand, SerializationFormatter = true)]
public virtual void GetObjectData(SerializationInfo info, StreamContext context)
{
info.AddValue(“Product ID”,productid);
                info.AddValue(“Price”,productprice);
info.AddValue(“Quantity”,productQuantity);
}

Responding to Serialization Events:
Serializing: Apply [OnSerializing] Attribute
Serialized: Apply [OnSerialized] Attribute

Deserializing: Apply [OnDeserialized] Attribute
Deserialized: Apply [OnDeserializing] Attribute

NOTE: This method is been called after IDeserializationCallback.OnDeserialization. Don’t use [OnDeserializing] attribute if Formatter other than BinarFormatter is used, in this case use OnDeserialization callback method.

Rules for Event handling:
• Method must accept StreamingContext object
• Returns void
• Proper attribute is being applied

How to change serialization based on context:
Specific Context information may be required to in order to deserialize an object. One can make those decisions himself in the GetObject method in which StreamingContext is provided. One can throw exception if the context information is not relevant.

To manipulate the Context information use the State bit and Set the status as required. These statuses are:

CrossProcessor, CrossMachine, File, Persistance, Remoting, Other, Close, CrossAppDomain, All.
One can use Context property of Formatters to alter context information before manipulation.

How to Create Custom Formatters:
                IFormatter, IGenericFormatter interface can be implemented. One can take advantage form static methods of FormatterServices class.

Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...

Text Encoding and Decoding using .Net

Namespace: System.Text To read a file, an application must write information about the encoding in which the file was written. So, the application that creates a file must write encoding information, otherwise viewer will see block and question marks in file. Unicode UTF-32 encoding : Represents a character as sequence of four bytes (32 bits). UTF32Encoding class can be used in that perspective. Unicode UTF-16 encoding : Represents a character in 16 bits. UnicodeEncoding class can be used to convert to and from UTF-16 encoding. Unicode UTF-8 encoding : Unicode UTF-8 uses 8-bit, 16-bit, 24-bit, and up to 48-bit encoding. Values 0 through 127 use 8-bit encoding and exactly match ASCII values, 128 through 2047 use 16-bit encoding, and values from 2048 and 65535 uses 24-bit encoding. UTF8Encoding class can be used to convert to and from UTF-8 encoding. ASCII encoding : ASCII encoding encodes Latin alphabets as single 7-Bit ASCII character. It is not well su...