AqlaSerializer is intended to serialize objects, not just data.
What the difference? Data serializers don't care much about language runtime specifics like references, inheritance, etc. In contrast, an object serializer should take such things into account.
AqlaSerializer primary goal is to support important .NET features like nested collections, multi-dimensional arrays, references, etc. And it still supports Google Protocol Buffers format.
Like protobuf-net AqlaSerializer makes possible to store objects as a small in size binary data (far smaller than xml). And it's more CPU effective than BinaryFormatter and other core .NET serializers (which could be unavailable on your target platform). Its format is designed to be: small in size - efficient data storage (far smaller than xml) cheap to process - both at the client and server platform independent - portable between different programming architectures extensible - to add new data to old messages.
The implementation is compatible with most of the .NET family, including .NET 2.0/3.0/3.5/4.0, Windows Phone 8, Silverlight, Xamarin.Android, etc. The code is heavily based on Marc Gravell's protobuf-net but there are a lot of improvements and fixes.
The original protobuf-net project contains many "red" unit tests but I managed to fix a lot of them.
Some build configurations may be not available through nuget, you can download their binaries manually from github (use Project Site link).
See the version list below for details.
Install-Package aqlaserializer -Version 220.127.116.11
dotnet add package aqlaserializer --version 18.104.22.168
<PackageReference Include="aqlaserializer" Version="22.214.171.124" />
paket add aqlaserializer --version 126.96.36.199
- 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
* 188.8.131.52: V2 release
- 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
* 184.108.40.206: V2 RC2
- Removing field won't break reference tracking.
* 220.127.116.11: V2 RC
- 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 in LateReference mode.
- 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.
- more effficient memory usage
- if writing stream CanSeek and CanRead the serializer may use it as a buffer when its own buffer grows too big
* 18.104.22.1688: merged changes from the fork origin (except DNX)
* 22.214.171.1243: fixed AsReferenceDefault correct usage for legacy protobuf-net attributes
- fixed issue when surrogated value was not correctly reference tracked
- add method is recognized not only on IEnumerable<T> but also on its inheritors like IReadOnlyCollection<T>
* 126.96.36.1997 - improvements in list handling, merged changes from original protobuf-net
* 188.8.131.52 - initial AqlaSerializer release
- aqla.runsharp (>= 184.108.40.206)