LabVIEW
BUG: PPL Built in 2017 only loads in 2019 if built with Debugging On
I've recently encountered an issue with one of the PPL's we use. I created a PPL that is used to track/create Pathloss calibration data. Underneath the hood it uses TDMS data to store the data on disk.
We built the source code in LabVIEW 2017 32-bit SP1, and build the PPL normally with debugging turned OFF. There is no fancy code involved, only just reading tdms, and manipulating arrays using built in LabVIEW functions. Building it with "Debugging" disabled builds fine. We can then call the code anywhere in LabVIEW 2017 both in the development environment and the runtime environment.
The problem comes when we want to use LabVIEW 2019 32-bit SP1. And we only run into issues when it's the development environment of LabVIEW 2019.
1. If we build a project, and insert the VI's in question from the 2017 PPL into LabVIEW 2019 they are broken.
2. If we run the VI's in TestStand with the LabVIEW Adapter set to Development they are broken.
3. If we run the VI's in TestStand with the LabVIEW Runtime Engine (version 19) it works.
4. If we rebuild the PPL's in LabVIEW 2017 with debugging turned on it works no matter what.
What is also odd, is if we use the VI's that don't work in 2019, and include them in a 2019 project, and then build that project (another PPL), it builds fine even with all the run arrows broken.
Error in Question:
Has anybody come across this and found a solution? For now we are just building the PPL with debugging turned on in LabVIEW 2017. We can not rebuild it in 2019 for now, because it supports multiple customers on multiple versions.
