LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI name collision using plugin type architecture

I am using LabVIEW 8 and am building an application that will use a
"plugin" architecture. There will be a main program built into an
executable that calls sub vi's that are in llb's. Some vi's in the
llb's will call DAQmx functions, others will do calculations, etc. Some
math functions will be done in the main program too.

The problem I am trying to address is how to deal with vi.lib vi's that
are used in the plugin llb vi's and the main program. For example, I
use Mean.vi in one of the plugin vi's as well as in the main program.
Where should Mean.vi be stored? A name collision occurs if it is in
more than one location (i.e. in a plugin llb and the main program
executable). This can get very complicated if many vi.lib vi's are used
in the plugin llb's and the main program executable. How can I
distribute vi.lib vi's that are required for my application to run? The
application builder is fine for simple distributions but breaking up
the application into several modules (llb's) that have functions (vi's)
like a dll has some great advantages.

As side issue, does anyone know of a way to assign a version number of
a llb file that is visible from its properties window in Windows?

0 Kudos
Message 1 of 2
(2,286 Views)
Duplicate.

___________________
Try to take over the world!
0 Kudos
Message 2 of 2
(2,274 Views)