Skip to main content

Serialization


What Is Serialization?

Serializing is the process of converting an object into a linear sequence of bytes that can be stored or transferred.
Deserializing is the process of converting a previously serialized sequence of bytes into an object.
 
These techniques convert objects into binary, SOAP, or Extensible Markup Language (XML) documents that can be easily stored, transferred, and retrieved.

The Following section is meant for Object Serialization and De-serialization

Serialization Format
                                     
Following are the two formatters that are available to be used in serialization/deserialization

BinaryFormatter: This formatter is the most efficient way to serialize objects that will be read by only .NET Framework–based applications. It converts the type into a stream of binary data.

SoapFormatter: This is XML-based formatter and is the most reliable way to serialize objects that will be transmitted across a network or read by non–.NET Framework applications.
 
How to Serialize an Object (Common for Binary and Soap Formatter)

The steps for serializing an object are as follows:
1. Create a stream object to hold the serialized output.
2. Create a BinaryFormatter object
3. Call the BinaryFormatter.Serialize method to serialize the object and output the result to the stream.


How to De-serialize an Object

De-serializing restores a saved object.
The steps for deserializing an object are as follows:
1. Create a stream object to read the serialized output.
2. Create a BinaryFormatter object.
3. Create a new object to store the deserialized data.
4. Call the BinaryFormatter.Deserialize method to deserialize the object, and cast it to the correct type.

Custom classes can be made serializable and deserializable by adding the Serializable attribute to the class.

If specific members are not to be used for serialization, add the NonSerialized attribute to the member as follows

[NonSerialized] {Modifier}{Return type} method name

Example:

Serialization
using System;
using System.Web;
using System.Web.UI;
using System.IO;
//this is for binary formatter
using System.Runtime.Serialization.Formatters.Binary;
//this is for Soap Formatter
using System.Runtime.Serialization.Formatters.Soap;

public partial class Serialize : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        string data = "Pradeep's Test For Serialization";
        FileStream fs = new FileStream("Pradeep.data", FileMode.Create);
        //Binary Formatter
        BinaryFormatter bf = new BinaryFormatter();
        //Soap Formatter (Uncomment if using Soap)
       // SoapFormatter sf=new SoapFormatter();
        //serialise using
        bf.Serialize(fs, data);
        //uncomment if using Soap
       // sf.Serialize(fs, data);
        fs.Close();
    }
}

 
De-serialization
 
Use the Following code to deserialize the data serialized above

FileStream fs = new FileStream("Pradeep.data", FileMode.Open);
BinaryFormatter bf = new BinaryFormatter();
Response.Write((string)bf.Deserialize(fs));//data is converted back to string




This article just covered the basics of Serialization. Shortly I’ll cover one more aspect of Serialization, the XMLSerialization.

After that, I’ll cover the Serialization options introduced new in .Net 3.5 namely the DataContractSerializer and NetDataContractSerializer.

Till then…Happy Coding!!!

Comments

Popular posts from this blog

Authentication using Social Networking portals(Facebook, Gmail, and Yahoo)

There are tons of sites, which offer sign on using the social networking site credentials (Facebook, gtalk, twitter and the list continues).It can be termed a “SINGLE SIGNON” and offers a lot of benefits compared to traditional database authentication approach. However, not storing user credentials in the DB imposes an additional risk. How to track who all logged into the system. Now the question is, which approach to follow. The best approach is to use inbuilt asp.net users for storing the logging info about user activities and using single signon technique for authentication. This article will explore the approach and provide the details of implementation using some third party libraries and customizing it to the requirements. The Authentication will be done using the following networking portals Yahoo  Gmail Facebook    Special thanks to my friend Sumit Khandelwal, for implementation of Facebook part (in fact he did it all!!) Except Facebook, all other ca...

WPF Overview-Part-II

This post is in continuation to the last post. In this Post I’ll be exploring the Dependency Properties Dependency properties are similar to CLR properties with more advanced and complex features. The main difference between the CLR properties and dependency properties is, that the value of a normal .NET property is read directly from a private member in your class, whereas the value of a DependencyProperty is resolved dynamically when calling the GetValue() method that is inherited from DependencyObject . In case this description did not make sense, no need to worry, It will become clear by the time you reach end of this article. How the Value is Resolved in Dependency properties Every time a dependency property is accessed, it internally resolves the value by following the precedence from high to low. It checks if a local value is available, if not, check if a custom style trigger is active and I the similar manner continues until it finds a value. At last the default value is alwa...

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...