aqlaserializer (nuget): 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 3.5/4.0/4.5, .NET Standard 2.1 (.NET Core 3/3.1, .NET 5, .NET 6), Windows Phone 8, Silverlight 5, Android, iOS, UAP. 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).
Keywords: Reflection.Emit|binary|serialization|protocol|buffers|protobuf|protobuf-net|deserialization|aqlaserializer|aqla|aqlasolutions|protocol-buffers|serializer