Using basic serialization we can have an attribute "Serializable"
at the class level. Using basic serialization, it is up to the .NET Framework
to take care of the serialization and de-serialization. But the problem with
this type of serialization is that we cannot have control over the
serialization algorithm. Another major issue with basic serialization is that we
have versioning issues like "System.Runtime.Serialization.SerializationException"
Possible Version mismatch. But basic serialization is the easiest way for
On other hand custom serialization gives us more control. As
we have seen in listing 1 and 2, we can implement the interface ISerializable
which gives us more control over the serialization algorithm. We can also avoid
the serialization exceptions with the custom serialization. Apart from these,
we have 4 attributes when applied to methods they are called in the process of
serialization. Let us see each one of them in detail.
– This attribute when put on a method, the method gets fired when the
de-serialization is completely done.
– When applied on a method this method is called during de-serialization of an
When applied on a method this method gets fired after the serialization process
– When applied on a method this is fired during the serialization process.
We can get maximum control over serialization and
deserialization process using the attributes.