-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do you have some solution like Data Contract Resolver? #299
Comments
related to #19 |
related to #300 |
@mgravell Did you have any idea? thanks |
Normally in protobuf-net , we never store explicit type information: we just store a numeric tag; the way we build the serializer currently means that you'd really need to register the known tags in advance (via the "include" functionality, usually via [ProtoInclude(...)] at compile time, although it can also be specified at runtime). What you are describing here sounds more like "any" (a protobuf feature). I haven't had need to implement good "any" support in protobuf-net, but that's something we could do - however, due to how protobuf objects work, this is more about arbitrary message types, not inheritance. What would help here is: what is the scenario you're trying to solve? |
I exactly want to resolve some problem like #300 many thanks to response |
@mgravell I think protobuf-net need some practice like WCF to support inheritance in clean way :) I think this feature must be add to https://github.com/protobuf-net/protobuf-net |
@mgravell Did you can help me to where this feature must be implemented? thanks |
@mgravell Did you can help me? thanks |
ITNOA
as you can see in https://learn.microsoft.com/en-us/archive/msdn-magazine/2011/february/msdn-magazine-data-contract-inheritance-known-types-and-the-generic-resolver#data-contract-resolvers
when WCF try to resolve inheritance in data contract, we have to define Data Contract Resolver like below
How to get same behavior in protobuf-net.Grpc?
The text was updated successfully, but these errors were encountered: