You can enable 'new protocol' specifying PackerCompatibilityOptions.None to Packer.Create method or SerializationContext.CompatibilityOptions.PackerCompatibilityOptions property. It is intended behavior to interop old bindings. Note that Unpacker always handle bin types.
I recognized the issue. Unpacker certainly recognize new binary type, but it handles it as raw type. It should always treat binary type as byte[], so I will fix it. Thanks!
Hi @yfakariya
From my understanding, MsgPack 5 supports distinction between string values to binary values.
How can I determinate what have I read from the stream?
I tried this code
But it tells me a string was written.
Thanks
The text was updated successfully, but these errors were encountered: