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 protobufs for each object in the client, just for display purposes. Thanks On Sep 29, 10:58 am, Marc Gravell <[email protected]> wrote: > 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-protobufs > > On Sep 29, 4:03 pm, "[email protected]" <[email protected]> > wrote: > > > 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
