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.

Labels:

Comments

Post a Comment

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...
Post a Comment
Continue Reading »

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 : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »