VI Links broken when using PPL

[Sam_Sharp]

I have a weird issue that I've noticed and not sure why/how it is happening:

I have some code modules that call VIs in a packed project library (PPL). This works fine in my development machine, but when I create the TestStand deployment, all of the PPL VIs are broken/cannot be found.

The VI Path is specified as 'My PPL.lvlibp\My VI.vi' (with no project) but when opening the sequence on the deployment machine, it appears as 'My PPL.lvlibp\My VI.vi\My VI.vi' (hence why it is broken) and I have to manually go through the sequences and fix the VI paths.

After much frustration, I was able to work around the issue by checking the 'Do not process this file or its dependencies' for the sequence that calls the VIs in the PPL but I don't think this is the right solution as that would mean it would then start to break if I also called standalone VIs / other code modules.

Any ideas?

[Nico011]

Hi Sam,

This is really strange. Try as I might, I can't get it to happen. Can you give me some help in replicating this?

How are you referencing the code modules? (Relative/Absolute Paths)

How is your PPL structured? (folders etc.)

What type of distribution are you creating?

When you create the distribution, does it function on the development machine using those files instead of the development files?

Thanks,

Nic

[Adam.B]

It happens that I am also seeing the exact same problem when building my deployments so I hope you don't mind me giving you the details of my situation:

• I'm building a deployment from a TS2014 workspace. My PPLs are referenced by relative paths in both the workspace and from the calling sequence files, and the deployed folder structure matches the source so that the PPL paths referenced by the sequence file shouldn't change at all when deployed.
• This problem happens with both flat PPLs and those containing subfolders inside, with subfolders the subfolder and VI name both get duplicated, e.g
  "<PPL name>.lvlibp\<PPL subfolder>\<VI name>.vi"
  becomes
  "<PPL name>.lvlibp\<PPL subfolder>\<VI name>.vi\<PPL subfolder>\<vi name>.vi"
• I'm creating a deployment installer.
• My sequence functions on the development machine using the source files, they are broken when the deployment tool copies them into the Target folder.

Thanks in advance for any help you can give with this issue.

Adam

[WireWeaver]

What version of TestStand are you using?

This sounds like CAR 533930, which was fixed in TestStand 2016. There is another forum post about it here.

Hope this helps!

Trent

[Nico011]

That would explain why I couldn't make it happen 

Nic