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...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

ASP.NET Working with Web Configuration Files

Our sites are configured based on hierarchy of XML configuration files. Machine.config is top level configuration file located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\machine.config These settings are framework level and common to all Windows, Console, Class Library, and Web application. Some of them could be overridden in Web.config while others are protected. Next in hierarchy is Root.config. It’s located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\web.config It contains default web server settings. Optionally one can add at root of all websites a web.config to provide general settings related to all sites. Optionally to provide more control on settings one can add web.config in each web site and for each folder in that web site. Processing the Configuration files:                       ...