I think I am confused. I thought that if a parent container was added as an additional export provider, a child container would have access to elements in the parent container and things added explicitly to the child. Here's some code:
var parentContainer = ((ExportingCompositionContainer)parent)._compositionContainer;
_compositionContainer = new CompositionContainer(_aggregateCatalog, parentContainer);
The "parent" is a wrapper with a property for the compositoin container it holds. That's why teh first line looks funny.
So, if I look at the parentContainer.Parts, I see what I expect. If I look at the resulting child (_compositionContainer in this context) I see no parts in the catalog.
I was exploring this becuase ImportMany was not working as expected.
My question at the moment is pretty basic. In the above, should the child container include all the parts of the parent?
If so, then I'd love some help figurig out what went wrong.
If not, I'm not sure I understand the usage of hierarchical containers and could use some information on how to make them work.