Karthik Sethuraman

Specify valid Name Types for ServiceInterfacePoint

1

In TAPI, the NameAndValue is currently being used as "KeyAndValue" - the valueName attribute of the data-type is specified to be object key. - So it would make sense to...

The current approach is to use the _name_ attribute, but it was noted in MEF that it would be better to have a separate attribute

With reference to clarification issues #145, #146, #147

Parent issue to resolve #115, #132 The current implementation is as per the containment hierarchy that was discussed/agreed by the TAPI design team during the TAPI IM design few months...