<SubVI: Save to 'destination' directory> How it works?

[MimiKLM]

Hi,

Quick question. Could you confirm or deny how that feature suppouse to work?

My understanding is: if my VIs which I have in my APPlication Directory (APPD) refer to others subVIs which are not in my APPD nor in its sub-directiories neither, then TestStand Deployment Utiliy collects all these scattered VIs into the 'DESTination' (DEST) folder and relink all my VIs and subVIs from APPD to VIs in DEST folder.

Am I right?

[Jervin Justin]

Hi MiniKLM,

Are you referring to the SubVI Location option in the LabVIEW VI Options Dialog of the Deployment Utility?


If so, what happens is that when you build a deployment, TestStand calls the LabVIEW Application Builder API to build a source distribution for the VIs that are code modules of your sequences and for VIs that are implicitly included in your workspace file (if you are deploying it). The App Builder will then try to find all dependent subVIs for these top level VIs and will dump them in the location specified. It will also relink the subVI calls in the top level VIs to point to the subVIs newly copied to the location specified.

Hope that helps!

[MimiKLM]

Thanks for response Jervin,

Let me reply in points:

1. Yes, I'm referrinig to the SubVI Location option in the LV VI Options Dialog of the Deployment Utility.

2. I forgot to tell you that I use version 4.0.1f, so I don't have options like Chech for Broken VI During Analysis, Check for Broken VIs After Build and Remove Unused VI Component.

3. Reffering to your advice. You wrote: when you build a deployment, TestStand calls the LabVIEW Application Builder API to build a source distribution for the VIs that are code modules of your sequences and for VIs that are implicitly included in your workspace file. Why then the result of that I receive a lot of errors about missing, broken and doubled VIs, whereas when I'm launching these VIs directly from the LV I don't came across these errors? What is the difference between LV Application Builder called from TS and calling files directly from LV?

4. The App Builder will then try to find all dependent subVIs for these top level VIs and will dump them in the location specified. It will also relink the subVI calls in the top level VIs to point to the subVIs newly copied to the location specified. OK, it is how I expected to be. Thanks for confirmation.

5. I started that thread as I part of other issue which I presented here. Could you have a look on that thread then? Many thanks in advance.