Thanks for the quick response Wes. I've taken a look at David Kean's blog post and yet I'm not sure if it's useful in my scenario.
Here's my scenario:
My host is a WCF service (itself hosted in IIS). It contains 2 "logic" components and these both share a dependency on an external data provider part. So for this host I need the imports to have CreationPolicy set to shared.
In the future, however, I might like to host one of the logic components in a different process and have it import the external data provider part as non-shared. Since the CreationPolicy is set inside the component, at the [Import] attribute, I cannot manage
it from the host. But it's the host that "decides" how to instantiate the imported external data provider.
Does this make sense? Is there maybe a better way to formalize my dependencies so that instantiation is controlled not by the importing part but by the host?