Sep 11, 2010 at 1:15 AM
Edited Sep 11, 2010 at 1:18 AM
Just stacking metadata key/value pair declarations (i.e. corresponding attributes) one above the other works fine, and as expected, in my case.
All my values are strings so I cannot say much on strong metadata types, even if I see no reason why other value types would be any different from values of string type.
When I enumerate the exports inside the container I get a dictionary of keys and values for metadata on each export. The key is the string (as expected) while the value is object since it can be any type.
Look at ContractBasedImportDefinition constructor.
Its metadata parameter is IEnumerable of KeyValuePairs and expects a CLR Type for each value so that I would say
you definitely can filter on metadata value type(s).