Application Builder and Library Dependencies

[John80]

I have installed the "Field R&S Services" Logger library via the VI Package Manager for LabVIEW 2018.  All works fine but when I create an Application (.exe) and try to run this on another machine that only has the LabVIEW runtime installed I get the following error:

Invoke Node in Logger.lvlib:File Start.vi->Top-Level.vi
<APPEND>
The front panel for <b>Z:\work\git\builds\LabviewLogging\My Application\LabviewLogging.exe\1abvi3w\vi.lib\Field R&D Services\Logger\Public\Action-Status\File Run.vi</b> could not be loaded but is required by this property or method.

The vi it is referring to exists in the Field R&S Services Logger library and contains a static vi reference that has me thinking is the reason that vi is not present

Does this mean I have to create an installer? Or is there something simpler that I can do in order to avoid having to run an installer each time I want to test my application on a target machine.

[Mark_Yedinak]

In your application builder do you mark the VIs that you load dynamically as "Always Include"?

[John80 · Accepted solution]

Okay, I found something that worked on the lavag.org forum:

https://lavag.org/topic/14151-build-specification-enable-debugging/?tab=comments#comment-85259

All I had to do was the first bullet point - set "Show front panel when called" for the vi 'File Run.vi' in the library directory (C:\Program Files (x86)\National Instruments\LabVIEW 2018\vi.lib\Field R&D Services\Logger\Public\Action-Status\File Run.vi) and it worked!