Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Place folder contents in destination" is not working for support files #57

Open
Sdusing7 opened this issue Jan 25, 2025 · 2 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@Sdusing7
Copy link

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:

Image

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

  1. Create a vi package build spec.
  2. Make a folder called "Examples" to deploy to the NI examples folder
  3. put a vi in the folder
  4. put a .txt file in the folder
  5. Set the Examples folder to "Place Folder Contents in Desintation"
  6. Run the build spec
  7. install the vip
  8. 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

@Tom-McQuillan
Copy link
Collaborator

Tom-McQuillan commented Feb 27, 2025

This is is a zip to reproduce the issue
Issue 57 Place Folder Contents in Destination.zip

Issue.57.mp4

@Tom-McQuillan 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
@Tom-McQuillan
Copy link
Collaborator

Richard Thomas has mentioned "Place Folder Contents in Destination" doesn't work for PPLs either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants