I can't reproduce this outputting a 0x0; my example is below, and
outputs 22-0A-12-08-73-6F-6D-65-43-69-74-79 - the null nested message is
simply completely omitted; the contents are:
- 2 bytes field-header and length-prefix for the location member
- 2 bytes field-header and length-prefix for the
Just for visibility; we've discussed this more on github, and it *looks* to
be a protostuff decoding issue, not a protobuf-net encoding issue; Johannes
will take our findings to protostuff for further investigation.
Arbitrary link is
arbitrary:
Hello everyone,
Firstly I need to apologize for any misuse or misunderstand of terms and
concepts. I'm mostly familiar with the Protocol Buffer implementations
protostuff and protobuf-net.
I have a case that two different implementations (the C# one: protobuf-net
and the Java one:
