You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fix for #61 ended up regressing the scenario when an ImportMany collection has no setter but needn't have one because it is set by the importing constructor.
The text was updated successfully, but these errors were encountered:
…rties
The case where this would actually work at runtime is when the MEF part's ImportingConstructor sets the value of the ImportMany property to an (empty) collection, in which case MEF will simply add elements to it and never have to access the setter.
Fixes#94
…rties
The case where this would actually work at runtime is when the MEF part's ImportingConstructor sets the value of the ImportMany property to an (empty) collection, in which case MEF will simply add elements to it and never have to access the setter.
Fixes#94
The fix for #61 ended up regressing the scenario when an
ImportMany
collection has no setter but needn't have one because it is set by the importing constructor.The text was updated successfully, but these errors were encountered: