Any particular reason you are putting the values in a dictionary? The way I see it, would it not be better to create a MetaData class and populate that instead? That would not mess up the deserialization and it would also make it a lot easier to query.
EDIT: Right, because of ProjectMetaDataFrom. I guess I should have read the entire question ;-)
Hi,
So this is a bug then. Problem occurs when we are deserializing the dictionary and it is static like that. Meaning it is already there. We need to fail silently here then I assume.
I have added a bug for this. We will look at it as soon as possible.
/Marcus
Ok, thanks! I forgot to mention that we are currently using version 8.0.3.411 of Find, if you need it for the bug report.
/Gustav
This is my scenario:
I am using UnifiedSearchFor to search in content types together with a few custom types. For one of the custom types (Employee) I want to show some additional info in the search hit compared to a hit for e.g a standard content page.
To do this I have added the following conventions:
where the extensionmethod EmployeeMetaData looks something like this:
So far so good, the UnifiedSearchHit.MetaData contains the info I want to show. However, when I call Client.Get(id) I get: "System.ArgumentException: An item with the same key has already been added".
Stack trace:
Is this some bug or am I simply doing this the wrong way?