I believe that the specifics are that a DLL of the exact same version of LV doesn't need to load the runtime into the LV dev environment. A DLL built with a different version of LV will load the appropriate runtime, since that is the version that the VIs must have.
So this doesn't help much in controlling it, but I think it explains why sometimes they are in the same memory space and sometimes in different ones. We don't have any mechanism in current LV for making VIs private to a DLL or LLB. A quick and dirty fix is to change the name of your subVIs, giving them a suffix, to make them private. Greg McKaskle
