10-02-2024 05:04 AM
Hi
I'm deploying TestStand 2016 SP1 projects to our production PCs.
We have multiple products to deploy on the same PC, so each product has a deployment.
My problem is the location of the SupportVIs folder on the production PC, I see the following two folders after a deployment:
The folder "TS-NC_DualEth_01B" is where all the VI's I wrote are located.
When running this on the deployment PC, all works well.
The issue is when installing the next deployment on the same PC, the SupportVIs folder gets written over and then the previous deployment fails "Cant find VIs".
How can I install the SupportVIs folder inside the same product folder "TS-NC_DualEth_01B", so it does not get written over by other deployments?
Thanx
Marinus
10-02-2024 06:16 AM
Don't think, what you are trying to achieve is actually a scalable design decision.
If the contents of TS-NC-DualEth_01B is identical for multiple deployments, this component should be a deployment itself to which all the others refer to.
If contents TS-NC-DualEth_01B differ between multple deplyoments, you have to deploy them seperately anyway
10-02-2024 06:48 AM
Hi Oli
TS-NC-DualEth_01B is one Product. Another product deployment might be TS-MA-BBRTU_02A
So each has a different name.
But anyway, I seem to solved my problem. I Added "TS-NC-DualEth_01B\SupportVIs" Labview Options.
Marinus