I recently upgraded my LabVIEW and TestStand environments from version 2019 to 2024 on a virtual machine. After the upgrade, I mass compiled my project, which includes multiple LabVIEW projects, VIs, and Python scripts, all contained within a single project folder. The mass compile completed without any errors. I also mass compiled some libraries under Programm files.
After the compilation, I created a deployment for my project. The deployment process completed successfully without any errors. However, when I tried to run my project post-deployment, I encountered a conflict in two specific LabVIEW projects. TestStand reported a conflict error for these projects.
To resolve the issue, I had to manually open these two LabVIEW projects (When I attempted to close them, I received a message stating that "an attribute of this project has changed," prompting me to save the projects). and saving them, then the conflict was resolved.
This process must be repeated each time I deploy my project, as these two specific projects consistently encounter this issue.
As Info: These two projects have several dependencies, including the OpenG library and NI data types.
I am unsure why only these two projects are affected in this way after deployment and would appreciate any insights or solutions.
Note:
After deployment, my project includes a new "Support VIs" folder that contains all the dependencies required by the project.
If i masscompile my project post deployment (before resolving conflict) i get following errors:
The VI expected to be at "project path" was loaded from "another project path" (VI name: Error Cluster From Error Code).
and both of this projects Path are containing the VI: "Error Cluster From Error Code"
