XML Serialization

  • Thread starter Thread starter Anuj Gupta via .NET 247
  • Start date Start date
A

Anuj Gupta via .NET 247

Can anyone please suggest 'why it is must to have a defualt constructor while serializing a class using XMLSerializer'?
 
Because the XmlSerializer deserializes an object by instantiating it (hence
the need for a default constructor) and then populating all of its
properties that can be written to. That's why the XmlSerializer won't
retain state for private members or any property that cannot be written to.

If you need an object that completely maintains its state (private members)
and does not rely on a default constructor, you should look at the
BinaryFormatter or the SoapFormatter. These can be found respectively in
the System.Runtime.Serialization.Formatters.Binary or
System.Runtime.Serialization.Formatters.Soap namespaces.

--
Ben Lucas
Lead Developer
Solien Technology, Inc.
www.solien.com

Anuj Gupta via .NET 247 said:
Can anyone please suggest 'why it is must to have a defualt constructor
Click to expand...
while serializing a class using XMLSerializer'?
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Configuring XML Serialization to not add an element 2
Different Serialization Technique In .NET 0
XmlSerialization to StringBuilder without Header information 1
Reasoning behind making XmlSerializer so “restrictive”? 2
XML Serialization 5
XmlSerializer FileNotFoundException 1
Using XmlSerializer for derived classes 2
Need to create a .NET object that will be serialized into a specific XML format 2

Back
Top