The main complexity arises from several instances of nested types
(which can be arrays). The protos below are not complete but should be
sufficient to give you the design in use here.
The 1st proto is complete. 2nd proto is much more detailed. I too was
thinking about reflection but without a ba
Well... how complex is the data? Reflection seems the most obvious
choice if it is available - especially since that will work well with
things like PropertyGrid (if you are in winforms). If I understood the
scenario better I may have more ideas...
Marc
On Sep 29, 6:39 pm, "test.f...@nomail.plea
Bummer.. It would've been a great feature. I'm faced with displaying
several complex nested protos and the simplest way would've been a 2
column list view that was populated by a generic proto reader.
I'm looking at Jon's solution, but I really don't want to have to
implement and maintain 2 prot
In protobuf-net? No. You could deserialize into the expected type and
use reflection, though. It is perhaps something I could consider
should I find time though - presumably in the non-type based branch
(experimental; unstable; incomplete...).
Jon's version may have other options here? dotnet-pro
Is there a way to generically read a protoBuf byte[] and extract a
field tag/name to value mapping?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to protob
