This library adds support for NodaTime types to MessagePack C#.
This library is provided in NuGet.
Targets .NET 10, .NET 8, .NET Standard 2.1 and .NET Standard 2.0.
In the Package Manager Console -
Install-Package MessagePack.NodaTime
or download directly from NuGet.
To use the NodaTime resolver, you will have to add it to the composite resolver, as shown in the example below:
CompositeResolver.RegisterAndSetAsDefault(
BuiltinResolver.Instance,
AttributeFormatterResolver.Instance,
SourceGeneratedFormatterResolver.Instance,
NodatimeResolver.Instance,
DynamicEnumAsStringResolver.Instance,
ContractlessStandardResolver.Instance
);For more information on either MessagePack or NodaTime, please follow the respective links below.
This is a quick guide on a basic serialization and de-serialization of a NodaTime type.
Instant inst = new Instant();
var bin = MessagePackSerializer.Serialize(inst);
var res = MessagePackSerializer.Deserialize<Instant>(bin);
// inst == resInsant, LocalTime, LocalDate, LocalDateTime,Offset, OffsetDateTime, Period and ZonedDateTime
As per the MessagePack spec, when we serialize a NodaTime type of LocalDateTime, LocalDate or Instant, an extension type of -1 is received meaning it is a MessagePack timestamp.
Timestamp spec can be found here.
An example of this in C# is shown below:
LocalDateTime ldt = LocalDateTime.FromDateTime(DateTime.Now);
// This date is within the range for timestamp32
var localDateTimeBinary = MessagePackSerializer.Serialize(ldt);
// Once serialized we can expect the format to be [0xd6, -1, data] (format, extension type, data in bytes),
// and ‘localDateTimeBinary’ to be a byte array of size 6In the same way we can support serialization from NodaTime (eg, LocalDate) to MessagePack (timestamp), the same is applied for deserialization.
From a timestamp, we can deserialize into a LocalDate (if time part is 0), LocalDateTime or an Instant.
From the snippet of code in serialization, shown below is deserialization:
var res = MessagePackSerializer.Deserialize<LocalDateTime>(localDateTimeBinary);❗ Deserializing a LocalDateTime into a LocalDate, will not work if the time value is not 0.
| NodaTime type | Serialization format |
|---|---|
| Instant | When an Instant is serialized, like LocalDateTime and LocalDate, it goes to timestamp format. Depending on the value of the Instant, it will fall into either timestamp 32, 64, or 96 format, as explained above under the Timestamp heading. |
| LocalDate | Once a LocalDate is serialized it is in timestamp format. Depending on the value of the LocalDate, it will fall into either timestamp 32, 64 or 96. LocalDate has no time values. |
| LocalDateTime | Once a LocalDate is serialized it is in timestamp format. This means an extension type of -1 will be received by MessagePack. LocalDateTime can be deserialized into a LocalDate if it has no time part. |
| LocalTime | LocalTime is serialized into an int64 (64 bit int). The int64 contains the LocalTime value in nanoseconds. |
| Offset | Offset is serialized into an int32 (32 bit int). The int32 contains the Offset value in seconds. |
| OffsetDateTime | When an Offset is serialized, it is split up into into the LocalDateTime and Offset parts. They are then serialized using there respective formatters. This means the serialized OffsetDateTime will be put into an array of 2 elements which looks like [timestamp, int32]. The Offset and LocalDateTime serialization is explained in the headings above. |
| Period | When the NodaTime type Period is serialized, it is split into a 'fixarray'. For a Period we have a 10 element array of four int32 amd six int64 respectively, represented in the order of → Years, Months, Weeks, Days, Hours, Minutes, Seconds, Milliseconds, Ticks, Nanoseconds. |
| ZonedDateTime | A ZonedDateTime is split up into LocalDateTime, an Offset and a string representing a Zone, during serialization. This means the ZonedDateTime is put into an array of 3 elements. Each NodaTime type is serialized using there respective formatters, while the string is serialized using the MessagePack base class into a 'fixstr'. |
While NodaTime supports nanoseconds accuracy, we currently do not. The lowest common level of precision between us and NodaTime is ticks. This means our serialization and deserialization process truncates at 100 nanoseconds because 100ns = 1 tick. Below are two examples explaining this:
LocalDateTime ldt = new LocalDateTime(2016, 08, 21, 0, 0, 0, 0).PlusNanoseconds(1)
var localDateTimeBinary = MessagePackSerializer.Serialize(ldt);
var result MessagePackSerializer.Deserialize<LocalDateTime>(localDateTimeBinary);
// ldt != result, nanosecond accuracy is lost in process.LocalDateTime ldt = new LocalDateTime(2016, 08, 21, 0, 0, 0, 0).PlusNanoseconds(100);
var localDateTimeBinary = MessagePackSerializer.Serialize(ldt);
var result = MessagePackSerializer.Deserialize<LocalDateTime>(localDateTimeBinary);
// ldt == result, returns truncated value equal to 1 tick.In the base MessagePack library, DateTime values are converted to UTC before being serialized. While using our library, you must specify DateTimeKind as UTC before serializing when using DateTime and the LocalDateTime type, and expect it as UTC when deserializing.
As explained previously, we use the timestamp format for some of our serialized NodaTime types. The timestamp format is interoperable with MessagePack for C#, the official MsgPack library and any other MessagePack implementations that support the extension type of -1.
Use the .NET SDK selected by global.json (C# 14) and open MessagePack.slnx.
The .NET 8 runtime is also required to run all tests.
dotnet build MessagePack.slnx --configuration Release
dotnet test --configuration Release --no-build --report-trx --results-directory TestResultsTests use TUnit on Microsoft.Testing.Platform v2, not VSTest. Existing serialization formats and target frameworks are preserved.
To collect Cobertura coverage with the existing MTP coverage extension:
dotnet test --configuration Release --no-build --report-trx --coverage --coverage-settings coverage.settings.xml --coverage-output-format cobertura --results-directory TestResultsCoverage includes the library, excluding generated code and test dependencies.
CI publishes the DotNET Tests check and test summary in the build workflow,
and saves TRX and Cobertura files as test-results and code-coverage artifacts.
Coverage for each test framework is uploaded to GitHub code coverage for same-repository
pull requests and master; fork pull requests still run tests and retain artifacts.
GitHub Code Quality/code coverage must be enabled for the repository.
This project is licensed under the MIT License - see the LICENSE.md file for details