Skip to main content

Difference between XML Serialization and Binary Serialization



XML Serialization
Binary Serialization (Soap)
No need of Serializable attribute on the class
Need Serializable attribute
Only public members are serialized
All members are serializes unless specified as NonSerializable
Class should have default public constructor and class itself should have public access.
No need of default constructor or public access
Namespace: System.XML,Serialization
Namespace: System.Runtime.Serialization.Formatteres.Binary (.Soap)
Outputfile is XML
Outputfile is Binary or XML for SOAP formatter
XMLSerializer need type of object to be serialized or deserialized
No need to specify type of object to be serialized or deserialized.
Support only IDesrializationCallback interface. No support for binary events.Binaryformatter support binary events. Soap formatter supports only IDeserializationCallback interface


Labels:

Comments

Syed Shakeer Hussain said…
First Point is wrong. XML need serializable attribute.
24 March 2016 at 22:23
Toolslick Technologies said…
The information you've provided is useful because it provides a wealth of knowledge that will be highly beneficial to me. Thank you for sharing Html Beautifier. Keep up the good work.
1 November 2021 at 07:32
Mohammed Shakil said…
I'd like to express my gratitude for writing such a helpful article. This article provided me with some useful knowledge. Thank you for sharing that. Keep up the good work. tool polishing India
3 November 2021 at 05:42
Post a Comment

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.
3 comments
Read more

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0
Post a Comment
Read more