Currently we have an issue when loading an object from sterling when one of the properties is a complex type with no parameterless constructor.
The issue is that Sterling uses Activator.CreateInstance in the deserialization - which needs a parameterless constructor on the instance it's creating.
Is there a reason why Sterling doesn't use:
object instance = System.Runtime.Serialization.FormatterServices.GetUninitializedObject(typeResolved);
... which doesn't require a parameterless constructor to create the instance, and is used by serializers such as the DataContractSerializer (as far as I understand)