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


Comments

First Point is wrong. XML need serializable attribute.
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.
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

Popular posts from this blog

Searching Unicode characters in Oracle table

Oracle implementation of Regular expression has no support for using hexadecimal code to search for Unicode characters. The only way to search for Unicode character is it use the character itself. Normally with Regular expression, you can use \x or \u followed by hexadecimal code to search for any character. E.g. \x20 will match space. But REGEXP_LIKE in Oracle does not support \x. You need to use unistr function to convert the code to equivalent character and then use it with REGEXP_LIKE. E.g. REGEXP_LIKE(source,'[' ||unistr('\0020')|| ']');

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

How to get started with .Net Core and Lambda functions?

 Recently I started experimenting with .Net Core and AWS Lambda functions, I thought I will share the steps I took to get started Tools to install .Net Core 3.1 -  https://dotnet.microsoft.com/download/dotnet-core/3.1 AWS CLI -  https://aws.amazon.com/cli/   AWS Account - 12 months Free Tier -  https://aws.amazon.com/free Terminal - on iOS I use iTerm2 -  https://www.iterm2.com   Once you installed the above tools, head to AWS console and login with your root account to create an account which will be used by AWS CLI. Please see steps here   Now you can configure AWS CLI as detailed here . Verify that you able to connect to AWS service using CLI. To make life little easy with dotnet core and Lambda functions, you need to install AWS Extensions nuget pack for .Net CLI dotnet tool install -g Amazon.Lambda.Tools You can also install templates to get started quickly  dotnet new -i Amazon.Lambda.Templates That's it. Now the fun part!!!  Creat...