I am creating some packages for our internal reuse code.
I create Package "Config Files". This package does not have any other package dependencies, and installs as expected (using custom directory, not under LabVIEW).
I create a second package, "File Paths", which calls a vi in the Config Files package. Since the Config Files package is installed, VIPM correctly says that the Config Files is a dependency.
When I go to build and install (using custom directory, not under LabVIEW) the File Path package, I see a copy of the vi from Config Files under the directory of File path, instead of the file that should have been used under the Config File path.
What I Expect:
C:\Config Files\test.vi
When Installed:
C:\File Paths\test.vi
I saw some older forum posts about Internal and external dependencies, but I do not see that option in LV 2019. Has this option been removed?