Are there any plans to expose these IntPtr fields as properties in a later version so we do not have to rely on reflection? Also, are there any plans on using {ReadOnly}Span/{ReadOnly}Memory in place of byte for BinaryAttachment? I am using pooled arrays to serialize our messages, but they are, most of the time, larger than the message size. It would be nice to not have to allocate arrays for setting onto messages.
The only workaround I have is to stackalloc the byte, copy from Span (into which the data was serialized), and then p/invoke setting of the binary attachment using the IntPtr of the stack-allocated byte.
We are using C# and .NET Framework 4.8.1. The business message library I am writing is being compiled as a .net standard 2.0 library.