wrong expacted Path for subVIs when VI is placed in a custom destination

[T.L. 0]

I want/have to build a package, where most of the VIs are located under LabVIEW ..\vi.lib path and some top VIs should be placed in "C:\ProgrammData\MyProject".

All VIs are placed at there correct destinations after installing my package(s).

 

BUT:

 

When I open my top level VIs from "C:\ProgrammData\MyProject" LabVIEW starts searching for the subVIs and finds them in "C:\Program Files (x86)\National Instruments\LabVIEW 2014\vi.lib\MyProject\.."

 

LabVIEW warns me for new dependency paths for my subVIs.

 

a) if I put all in a single package the expacted path is "C:\labview\vi.lib\MyProject.."

if I build 2 packages 1st installing vi.lib-stuff and 2nd installing top level VIs the expacted path is "..\..\..\..\..\..\MyProject.."

 

Why are my top VIs not properly relinked to there subVIs?

How can I get them linked correctly?

 

Best regards

Thomas

[Ashish 7]

What I understand is: after installation, the Top Level VI links to the newly installed VIs under vilib and provides warning about the new linkage. Is that correct?

 

Also, it seems that building 2 packages is also linking correctly to the installed VIs under "..\..\..\..\..\..\MyProject.."

 

Can you help clarify the issue?

[T.L. 0]

Hello Ashish,

 

when I put everything into a single package, the VIs NOT placed under <LabVIEW>\vi.lib are NOT correct relinked to them. When opening the top level VIs LabVIEW starts searching for the VIs which are now installed in LabVIEWs folder structure.

 

Actually I have this workaround:

I have to 2 projects and 2 packages.

In 1st project/package everything to put into LabVIEWs folder structure.

And a 2nd project/package to use the VIs previously installed. This installs my code to "C:\ProgrammData\MyProject\..".

 

Does it help?

 

Best regards

Thomas

[Ashish 7]

Thomas,

 

Ok. So, you are concerned about the top level VI searching for VIs after package installation and you are thinking that it will possibly link to wrong VIs.

 

Typically VIPM should mass compile after package installation in order to ensure that the newly installed package is linked correctly.

 

Do you see "mass compiling" in the VIPM status bar at the bottom during package installation?

[T.L. 0]

Hi Ashish,

 

mass compiling was activated. All VIs under <LabVIEW> are mass compiled while installation. Only VIs placed in custom folders are not mass compiled and relinked.

 

Best Regards

Thomas

[Ashish 7]

Thomas,

 

We were able to reproduce the behavior and recorded it as Case 16585 for consideration to be fixed in future.

 

We will notify you when we have the fix.

 

Till then, sorry for inconvenience.