Hi all!
I have been recenty submerging into SMO stuff and I fing it a bit unclear of how dependencies are managed in SMO.
I attempt to design a system where a partucular module (SMO) has several "by composition" dependencies which I easily can create and maintain with framework functionality. either by setting them up as static dependencies in "enumerate static dependencies.vi" or as dynamic dependency launch. As it is by composition relation, I am completely satisfied of register mainaining lifetime of those dependencies.
However, I want this module (module A) to to contain as well a module coupled by aggregation (module B). I.e. I want module A to have access to reference and functions of module B, but do not shut it down at the end of module A lifetime.
I have a suspicion, that "shared resource" is a keyword in here, but unfortunatyely I have failed to figure out it's functionality.
Could someone help me with understanding how this part of SMO engine works?
