nanoFramework.System.Runtime.Serialization
1.0.36
Prefix Reserved
dotnet add package nanoFramework.System.Runtime.Serialization --version 1.0.36
NuGet\Install-Package nanoFramework.System.Runtime.Serialization -Version 1.0.36
<PackageReference Include="nanoFramework.System.Runtime.Serialization" Version="1.0.36" />
paket add nanoFramework.System.Runtime.Serialization --version 1.0.36
#r "nuget: nanoFramework.System.Runtime.Serialization, 1.0.36"
// Install nanoFramework.System.Runtime.Serialization as a Cake Addin #addin nuget:?package=nanoFramework.System.Runtime.Serialization&version=1.0.36 // Install nanoFramework.System.Runtime.Serialization as a Cake Tool #tool nuget:?package=nanoFramework.System.Runtime.Serialization&version=1.0.36
Welcome to the .NET nanoFramework System.Runtime.Serialization repository
Build status
Component | Build Status | NuGet Package |
---|---|---|
nanoFramework.System.Runtime.Serialization |
Usage
The BinaryFormatter class serializes and deserializes an object, or an entire graph of connected objects, in binary format. This allows a compact storage or transition. Because it's implemented in native code, execution of serialization and deserialization operations are blazing fast.
The only requirement is to decorate a class or some of it's fields with the [Serializable]
attribute.
Other attributes are available to provide hints to the serialization engine so the serialization data it's reduced as much as possible. More on this on the next section.
Native support for this feature it's available in all targets that have support for reflection enabled, unless support for this has been disabled by a build option.
Warning the implementation of binary serialization for .NET nanoFramework is NOT compatible with the one of .NET Framework or .NET Core, meaning that it's not possible to use it to exchange data between the two frameworks. A helper class is available for .NET Framework and .NET Core to serializes and deserialize data coming from (or sent to) nanoFramework devices. More on this in the respective section bellow.
Serializing a class
Follows a Person
class that will be used in the following examples.
[Serializable]
public class Person
{
public string FirstName { get; set; }
public string LastName { get; set; }
public string Address;
public DateTime Birthday { get; set; }
public int ID { get; set; }
public string[] ArrayProperty { get; set; }
public Person Friend { get; set; }
}
To serialize it, simply call the method Serialize()
and pass the class instance. Like this:
var nestedTestClass = new Person()
{
FirstName = "John",
LastName = "Doe",
Birthday = new DateTime(1988, 4, 23),
ID = 2700,
Address = null,
ArrayProperty = new string[] { "hello", "world" },
Friend = new Person()
{
FirstName = "Bob",
LastName = "Smith",
Birthday = new DateTime(1983, 7, 3),
ID = 2000,
Address = "123 Some St",
ArrayProperty = new string[] { "hi", "planet" },
}
};
byte[] serializedPerson = BinaryFormatter.Serialize(nestedTestClass);
The serializedPerson
byte array above will contain the binary representation of the nestedTestClass
.
Note As default all properties and fields in a serializable class will be serialized unless they are decorated with the
NonSerialized
attribute.
Deserializing a class
In order to deserialize a class from it's binary representation to an instance of the class, call the Deserialize()
method and pass the binary representation.
[Serializable]
Person anotherPerson = (Person)BinaryFormatter.Deserialize(serializedPerson);
Serialization hints
There are optional attributes that can be used to provide hints to the serialization engine so the serialization data it's reduced as much as possible.
Taking the Person
class, follows the optimizations that are possible with the above example:
[Serializable]
public class Person
{
public string FirstName { get; set; }
public string LastName { get; set; }
public string Address;
public DateTime Birthday { get; set; }
[SerializationHints(RangeBias = 2000)]
public int ID { get; set; }
[SerializationHints(ArraySize = 2)]
public string[] ArrayProperty { get; set; }
public Person Friend { get; set; }
}
The SerializationHints
has several options to improve the data packing.
Looking at the ID
property above, which is of int
type, without any optimization it takes 32bits to store. Now, this is used to store an ID which, let's assume for the sake of the example that only store IDs bigger than 2000.
Using the RangeBias with a value of 2000
that value will be subtracted to the value being stored.
In the code above, the ID with value 2700, would be serialized as (2700 - 2700 = 700) which can be stored as 16bits value instead of the 32bits that it would initially take.
Another serialization hint is the array size. For the ArrayProperty
let's assume that it will be always contain 2 elements.
Decorating it with ArraySize
and the size of the array, will store that information as part of the serialization data thus saving space that otherwise would be wasted with a generic count for the size of the array.
Using it from .NET Framework or .NET Core
A helper class for .NET Framework or .NET Core (distributed as NuGet package) is available to serialize and deserialize data coming from (or sent to) nanoFramework devices.
The usage it's exactly the same as with the code running in the nanoFramework device.
To serialize a class:
var binaryFormatter = new BinaryFormatter();
var serializedPerson = binaryFormatter.Serialize(personOne);
To deserialize a binary representation back to a C# class:
var binaryFormatter = new BinaryFormatter();
var newPersonOne = binaryFormatter.Deserialize(UnitTestHelper.PersonOneSerialized) as Person;
It is recommended that the source code for the classes being exchanged is the same in the projects for both frameworks. To accomplish this one can use any of the usual approaches, like shared projects or linked files.
Warning Make sure the fully qualified name of the class is the same at both ends. Failing to do so will prevent properly deserialize the data. This is another good reason for sharing the same code file in both projects.
A detailed example of this can be found in the Unit Tests projects for the BinaryFormatter. They are using both techniques there.
- Unit Test project for the Helper library
- Unit Test project for nanoFramework library
Feedback and documentation
For documentation, providing feedback, issues and finding out how to contribute please refer to the Home repo.
Join our Discord community here.
Credits
The list of contributors to this project can be found at CONTRIBUTORS.
License
The nanoFramework Class Libraries are licensed under the MIT license.
Code of Conduct
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behaviour in our community. For more information see the .NET Foundation Code of Conduct.
.NET Foundation
This project is supported by the .NET Foundation.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net is compatible. |
-
- nanoFramework.CoreLibrary (>= 1.15.5)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.