You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Short Description of the Bug (in one or two sentences)
The "Place Folder Contents in Destination" in the VIPB "Source File Settings" window is not working for lvproj files, text files, and potentially other types of non-LabVIEW files. It is working for .vi files at least. This obviously causes issues if you deploy a lvproj file and it doesn't get relocated properly relative to the vi's it contains. This can also cause problems if you have a vi that's expecting a .txt file next to it but these get deployed to different locations.
Virtualization or Processor Version Information
Running on Windows Host
Steps To Reproduce
Create a vi package build spec.
Make a folder called "Examples" to deploy to the NI examples folder
put a vi in the folder
put a .txt file in the folder
Set the Examples folder to "Place Folder Contents in Desintation"
Run the build spec
install the vip
Notice that the deployment location for the txt file is still contained within the parent "Examples" folder even though it was supposed to place contents.
Expected behavior
I expect lvproj files, txt files, etc. to be placed the same way as vi's, where if they are in a folder marked as "Place folder contents in Destination" in the vipb spec, that folder should not contain it on deployment.
Actual Behavior
VI deployments work just fine when using the "Place folder contents in Destination" feature. However, .lvproj and .txt files do not as expected. They act as if that "Place folder contents in Destination" feature was not checked.
Anything else you'd like us to know?
Please add anything else you'd like us to know
The text was updated successfully, but these errors were encountered:
Tom-McQuillan
changed the title
"Place folder contents in destination" is not working for lvproj and text files (vi's work just fine)
"Place folder contents in destination" is not working for support files
Mar 4, 2025
Short Description of the Bug (in one or two sentences)
The "Place Folder Contents in Destination" in the VIPB "Source File Settings" window is not working for lvproj files, text files, and potentially other types of non-LabVIEW files. It is working for .vi files at least. This obviously causes issues if you deploy a lvproj file and it doesn't get relocated properly relative to the vi's it contains. This can also cause problems if you have a vi that's expecting a .txt file next to it but these get deployed to different locations.
Here is an example that shows the problem:
Problem identified in this Discord thread: https://discord.com/channels/1013126142166831175/1020105609946857483/1332518691643850762
Version Information
VIPM 2024.1 f1 (build 2637)
Operating System Version:
Windows 11
LabVIEW Version:
LV2023 Q1
LabVIEW Bitness:
64-bit LabVIEW
Virtualization or Processor Version Information
Running on Windows Host
Steps To Reproduce
Expected behavior
I expect lvproj files, txt files, etc. to be placed the same way as vi's, where if they are in a folder marked as "Place folder contents in Destination" in the vipb spec, that folder should not contain it on deployment.
Actual Behavior
VI deployments work just fine when using the "Place folder contents in Destination" feature. However, .lvproj and .txt files do not as expected. They act as if that "Place folder contents in Destination" feature was not checked.
Anything else you'd like us to know?
The text was updated successfully, but these errors were encountered: