This is specific to protobuf-net. The library does not currently expose any custom serialization extension point; to do that in a way that is genuinely useful, while not allowing the caller to break the wire format, is quite tricky. To date: it hasn't been necessary. If you can clarify *why* you feel you need that, I might be able to help more. At the moment, the idea is: you let the serializer know the model (whether that is explicit configuration, attribute-based configuration, or inference from constructors), and the the serializer worries about the rest.
Marc (protobuf-net) On 11 Aug 2014 18:07, <[email protected]> wrote: > Hi everyone, > My problem is, that i can only determine at runtime how to serialize a > certain class, called A for clarity. > Accordingly, I was hoping for a way to tell the RuntimeTypeModel how to > serialize A through a function/method call, for example by passing a > delegate to it, or sth. similar. > Is this possible? And if so, how? > > Thank you for your time > Jens > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
