You've minified your data ! The environment thanks you, if the size of your files is important consider the MessagePack format also handled by Xsd2code++ it is the smallest of all formats in our tool. / /// Test whether Name should be serialized /// public virtual bool ShouldSerializeName() / /// Test whether SKU should be serialized /// public virtual bool ShouldSerializeSKU() / /// Test whether qty should be serialized /// public virtual bool ShouldSerializeqty() Public partial class Product : EntityBase Here is a summary table of how the ShouldSerialize methods will inform the serializer to ignore the property : For a null type, if it has no value, it will be ignored. For a collection with no element, it will be ignored. Similarly if a numeric type is at its default value, it will be ignored. If a string type is null or empty the method will return false. This method is invoked by serializing to each of the inspected properties. The ShouldSerialize option allows to generate a method named ShouldSerialize depending on the type.In the JSon Attribute section, enable the option (DefaultValueHandling=Ignore, NullValueHandling=Ignore).In the Serialization section, activate the option ShouldSerialize (IgnoreEmt圜ollection, IgnoreEmpt圜omplexType, IgnoreEnumType, IgnoreNullable, IgnoreSimpleType, IgnoreEmtytring to true) the individual effect of theses settings can be found in here.
NET objects to JSON or XML is that the JSON/XML ends up containing a lot of unwanted properties and values. To solve the issue of unwanted JSON/XML, xsd2code has a range of built-in options to fine-tune what gets written from a serialized object.
One of the common problems encountered when serializing.