Classes in llb or multiple classes in same folder?

Question

Hi all,
In our main program there is an option to dynamically load a subvi given to us by our customer (so we don't know it or have it in advance). We discovered that for the subvi to load properly ALL its subvis and dlls need to be in the same folder. In order to not have thousands of VIs in the folder, we usually worked around this by putting all the subvis in an llb in the same folder. The subvi to load needs to be outside the llb, but all the rest is in an llb in the same folder. So far, so good.
I am writing in LVOOP a subvi to load in this way. Therefore, it has a number of classes. And I can't put all the classes in an llb because I have override VIs therefore I have a number of VIs called, for example, "Get". However, If they are not in the same folder as my subvi, the subvi does not load properly at runtime. Catch 22.
So my questions:
1. Is there a way to define a "namespace" for each class so they can be in the same folder without changing names? I thought this was inherent because of the class_name::class_method syntax, but apparently it's not...
2. If I put each class into an lvlib, will it ruin the override and dynamic dispatching VIs?
3. Does anyone have any other solutions to this problem?
Thanks all,
Danielle
"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett

Answer 1

Hi again,
I have prepared pretty simple project (actually based on well known example from NI - "Dynamic Dispatching")
Here two classes, and each class contain the member "Get Cargo Capacity.vi":
I have also created two Build specs. One is for single "stand alone executable, and another one for exe + 2 llbs, so each class targeted to own LLB.
See what happened:
LabVIEW 8.2:
Stand alone executable:
 because LabVIEW unable to store both Get Cargo Capacity VIs together in exe, they stored outside of exe in \data directory
Executable with LLBs:
LabVIEW still unable to put each member in own llb.
Take a note that in Application Builder settings was:
I will classify this behavior as clear bug.
LabVIEW 8.6:
Stand Alone executable:
LabVIEW still have collision, but now we have Warning (in LabVIEW 8.2 such warning is missing).
Also take a note, that now Get Cargo Capacity.vi placed outside of \data folder.
Build with LLBs:
That is what I have expected: now each class stored in own LLB (they linked together due to classes hierarchy of course). Take a note, that no any conflict warnings appear. Application still working.
LabVIEW 2009:
Stand Alone executable:
Now LabVIEW able to store both member in executable together (even with same name). Great!
Executable with LLB:
No differences in comparison with 8.6
One more test: Stand alone executable with LabVIEW 8.x layout:
Also no differences with LabVIEW 8.6, and all warnings are here:
Not sure that information above was helpful for you, anyway thanks for reading... 
If you have another trouble, feel free to modify one of the attached example and post it here for illustration.
Andrey.
Attachments:
DynDispatch82-90.zip ‏216 KB