Can Not execute a TS Sequence File with VIs that are already being compile in my Custom TS Operator Interface

Question

I have build a custom TS Operator Interface (Executable) with some custom VI(s)(GOOP VIs). I want to be able to call the same custom VI(s) from Teststand Sequences. When i try ti launch the sequence from my TS OI i got an error message, because LabVIEW Run Time find the same VI(s) from two different location : the OI and the sequence.
I would like to know, that is the best approach to resolve this problem.
For the moment i got two solutions :
(1) dynamically calling the VI(s) in the OI (executable)
(2)Changing the name of the VIs in the TS sequence.
I would like to know if it exist an another solution ?
thank you
derek

Answer 1

For the moment the VI�s that are shared between the sequencefile�s and the operator interface, are used as code module in the sequencefile�s (not as sub vi in the code module).
On the target system I will got my custom operator interface (which is build from the Testexec.llb + my goop VI�s). My goop VI�s are statically link to my operator interface.
(I will say that my executable are on the C drive : C:\Testexec.exe)
My sequencefile�s and the differents VI�s of each step is deploy with the TestStand deployment wizard. A library with all the vi�s call by the sequencefiles are group in SupportVIs.llb. (the sequencefiles and the VI�s library are on the C drive too)
For exemple I will say that I got a foo.vi (goop
method) which is build in the operator interface testexec.exe. The same foo.vi is call (as code module) by a step of one of my sequencefile�s.
When I try to launch the sequence with the operator interface, The LabVIEW Run Time inform me that he can�t load step "foo" of sequence �MainSequence� because he find 2 VI�s with the same name in 2 different location (C:\Testexec.exe\foo.vi) and (C:\SupportVIs.llb\foo.vi.
If you got a sample example, i will be glad to see it.
Thank you Ray for your help.
Derek