I\'m implementing a factory pattern for 3 different cryptography classes. The factory will determine which one to create and then get a serialized instance of the correct cl
Yes, the XmlSerializer requires a parameterless constructor to exist in order for the serialization to work.
From the following answer: Why XML-Serializable class need a parameterless constructor
During an object's de-serialization, the class responsible for de-serializing an object creates an instance of the serialized class and then proceeds to populate the serialized fields and properties only after acquiring an instance to populate.
You can make your constructor private or internal if you want, just so long as its parameterless.
For anyone who is still looking a few years later, the answer is now FormatterServices.GetUninitializedObject. Be careful with it, as this is just a piece of memory set to all nulls and zeros and if a field in the object's default value is something other than zero, it might be set wrong: "Because the new instance of the object is initialized to zero and no constructors are run, the object might not represent a state that is regarded as valid by that object."
DataContractSerializer does not require parameterless constructor. What it instead requires are special attributes of class.
Are PgpPublicKey
and PgpPrivateKey
classes defined by you? Simply add parameterless constructors to them.
They can be private if you don't want to make them accessible from outside. The deserializer can still access them.
Any Serializer Class need a parameterless constructor because, while deserializing it create an empty new instance, then it copies every public property taken from seialized data.
You can easily make the constructor private, if you want to avoid to create it without parameters.
EX:
public class PgpPublicKey
{
public PgpPublicKey(PublicKeyAlgorithmTag algorithm, AsymmetricKeyParameter pubKey, DateTime time);
private PgpPublicKey();
// cut other methods
}