AqlaSerializer

• dynamic string reference tracking fix
• UseBackingFieldsIfNoSetter parameter is removed and enabled by default

AqlaSerializer

• AutoTuple nullables serialization fix
• Stream.Position is not used unless it's necessary

AqlaSerializer

• interfaces without subtypes and System.Object use dynamic type by default
• support for ISet, IReadOnlySet, IReadOnlyDictionary
• arrays can be deserialized into IList fields
• bumped minimum supported .NET Framework version to 3.5 (.NET Core 3 is still supported)
• Android build now uses PCL so no dynamic compilation is possible there

Full Changelog: v.2.0.1.969...v.2.0.1.1031

AqlaSerializer

Support for .NET Standard including .NET Core 3 and .NET 5

AqlaSerializer v.2.0.0.372 Stable

• Types lookup optimization for RuntimeTypeModel
• RuntimeTypeModel.Add allows to specify different type family filters or custom filter
• fixed concurrency bug when not final version of RootSerializer was published to clients

AqlaSerializer v.2.0.0.245 Stable

• snk sign fixed

AqlaSerializer v.2.0.0.234 Stable

• Improved compiled dll output size, compilation and cold run speed
• Added an option CompilerOptions.AlsoCompileInPlace (default: true)
• dlls for Xamarin.Android for emit support
• RunSharp dependency updated

AqlaSerializer v.2.0.0.227 Stable

• Added CompileOptions.IterativeMode
• Fixed incorrect IL generated when list.Add method has a return value
• Fixed incorrect behavior of model.CloneAsUnfrozen
• Indexers won't be added as implicit fields
• Enum flags for model ids, see model.SetEnumFlagModelId
• RunSharp dependency updated

AqlaSerializer v.2.0.0.186 RC2

Fixed #13 - removing field won't break reference tracking

AqlaSerializer v.2.0.0.96 RC1

This V2.0.0.96 release changelog:

• fixed subtypes in debug schema generation.
• added a check when RootSerializer is incorrectly used instead of base type serializer.
• root/concrete serializers will be correctly chosen for collections.

Full V2 changelog:

• Google Protocol Buffers format support is back (I've reconsidered this) - (de)serialization.
• Nested collections.
• Multi-dimensional arrays.
• Improved reference tracking (e.g. surrogate fix and referencing arrays from inside themselves).
• Improved versioning (e.g. between reference-nonreference-null-nonnull-dynamic).
• Optimizations for better output size.
• Collection subtypes (will read subtype number to create correct concrete type).
• Array types may be registered as collections and use full set of features (null support, etc) even when passed as root objects.
• Primitive types are allowed to be set to fields marked as dynamic type.
• Reference serialization will avoid using too much recursion #1.
• Possibility to specify different attribute sets for different models (see ModelId property on attributes).
• Attributes to specify behavior on collection and collection elements (and nested) separately.
• Significant performance improvements.