Yes, OverwriteList should fix this. IgnoreListHandling does something very
different that doesn't apply here (see the intellisense comments for full
On 19 Sep 2013 17:21, "David Deutsch" <da...@reverenddave.com> wrote:
> So I *think* what is happening is that protobuf does a get of the property
> because it is a dictionary (actually, a dictionary of dictionaries). So
> what it is trying to do is grab the dictionary and populate it. It does not
> set the dictionary back to the original member because it must assume that
> I already have a handle to that dictionary. Problem is, I generate/consume
> the dictionary dynamically. Looks like there may be a way around this in v2
> with IgnoreListHandling and/or OverwriteList.
> On Wednesday, September 18, 2013 5:09:39 PM UTC-4, David Deutsch wrote:
>> I know this is a long shot, but is there any reason protobuf-net would
>> call the getter of a property on deserialization, and not the setter? Most
>> of my properties serialize and deserialize fine, but for one particular
>> property only the getter is called, and thus deserialization fails.
> 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 protobuf+unsubscr...@googlegroups.com.
> To post to this group, send email to email@example.com.
> Visit this group at http://groups.google.com/group/protobuf.
> For more options, visit https://groups.google.com/groups/opt_out.
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 post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/groups/opt_out.