Going from development to runtime engine only

[pinkfloydwalsh]

I have several top level VIs that call SubVIs from vi.lib. This is fine in the development environment
but when I go to a runtime only machine those VIs do not exist. I have written code to pull all the code
from vi.lib that my top level VIs need. I place all those VI's in a directory MYVILIB.

When I try to mass compile my top level VIs still find their subVIs in vi.lib. How can I tell those
top level VI's to look in the MYBILIB for those.

I have tried changing the search path so that MYVILIB is 1st in the list, but that does not seem to work.

[Joe_H]

---

@pinkfloydwalsh wrote:
I have written code to pull all the code from vi.lib that my top level VIs need.



I do not understand why you wrote code for this but you could try going to file/save with options/
Then from there you can choose how you want to save it, I would choose application distribution and uncheck the remove diagram. that way you will not have to keep up with two LLB one for the programming machine and one for the application machine, try saving like that first then let me know if works or not and we can go from there

[Dennis_Knutson]

Did you use the app builder to create an exe or are you trying to run a VI/LLB with just the run-time engine? You can't do the second option.

[pinkfloydwalsh]

Actually we are tired of how poorly the TestStand Delpoyment Utility works so we are trying to write a custom one.
I have everything working as far as scanning my TS scripts for top level VIs then pulling the VI.lib stuff into
a specific diretory. This is the same thing that the TS Deploy does. My last step is to get my VIs to us the files in
the new diretory vs VI.lib.

[pinkfloydwalsh]

You can run VIs with just a LabView runtime engine. The problem is getting them launched. We are using
TestStand to launch them.

[Dennis_Knutson]

Okay, I think I see what you're doing. Quick and dirty way is to temporarily rename vi.lib folder (i.e. _vi.lib) and then open your top level VI. If it asks for the VIs, point it to your .llb. If you were to do this on the deployment pc, where you woudn't normally have LabVIEW installed, it would search for the missing VIs in the llb if it's in the same folder as the main VI.

[pinkfloydwalsh]

We have thought of renaming vi.lib and instr.lib and user.lib, but were worried about a crash and then not getting them
named back.

[Dennis_Knutson]

You won't get a crash and you can always rename the folders after you've updated your main VI and saved it.

I know all about TestStand and the LabVIEW adapter. I've been using it since version 1.0. What confused me at first was that you didn't mention TestStand - just that you were trying to open a VI with just the run-time engine.

[pinkfloydwalsh]

So how does TestStand accomplish this when you do a deployment?

[pinkfloydwalsh]

Thanks for everybodies help, but I think I cracked the nut.

Here were my steps:

1) In a VI open a reference to all the files in MYVILIB dir.
2) Do a Save Instrument Property Node passing it the location of MYVILIB\file.