asthomas

This is further complicated by the requirement that an NDEATH message cannot include a sequence number. The consequence seems to be that it is impossible to build both a valid...

[Edited - original post confused the the .proto file with the behaviour of protoc] Before I can answer that question, I need to know which .proto file I should be...

I decided to take a look at the Google Protobuf spec. The Protobuf 3 spec contains this entry: > Note that for scalar message fields, once a message is parsed...

@MRIIOT - Spec section 4.2.1 says this: > [tck-id-topics-ndeath-payload] The NDEATH message contains a very simple payload that MUST only include a single metric, the bdSeq number, so that the...

Good link. That could be the winner. I found the optional field description in the proto3 docs now that I know what to look for, so it looks like just...

I can confirm that making Seq and both Timestamps optional in sparkplug_b_c_sharp.proto has resolved the issue for me with the latest protoc and Protobuf version 3.

It is. Essentially the optional flag in proto3 reinstates the behaviour of proto2, where in addition to having a value a member may also be unset. Unset values are excluded...

Thanks for responding. The bug has gone away. The only thing I did was to comment out some lines in MainPage.xaml and then rebuild. After that, I uncommented those same...

That might be possible. I'll post if I can get you a repro case.