06-21-2021 06:08 PM - edited 06-21-2021 06:22 PM
So I fixed some bugs and rebuild and installed one of my executables (all in LabVIEW 2020 SP1).
After installation, I ran it and was surprised that it was running under the (potentially unstable?) LabVIEW 2021 beta runtime.
Thinking that I accidentally built it using the beta, I rebuild everything, installed the app, but nothing changed.
Inspecting more closely, the exe build spec had the "allow future runtime versions" checked, so that's probably the reason.
Apparently, if the correct runtime (2020 SP1) AND a newer runtime (2021 beta) is available, it will grab the newest, even if that is only a beta.
Wouldn't it make more sense to primarily use the matching runtime and only grab a newer one if the correct runtime is not available on a system.
Oh well, the old dog learned something new. 😄
06-22-2021 04:24 AM
There was some discussion about this over in this idea exchange thread: Add ability to select which version of LabVIEW Runtime is compatible with executable
It addresses the issue you're describing.
06-22-2021 10:25 AM
Thanks. I missed that discussion (or forgot about it).
(Fortunately, this is a public beta (No NDA), otherwise I would have another problem. This was on my 16 core dual Xeon and one of the students is using this program for very CPU intensive, highly parallelized fitting of complicated models using a different windows account. (I still work mostly at home, so this is good hardware utilization 🙂 ). Since the "about" window and my indicator of version details now glaringly advertises 2021beta, this would have been an accidental NDA violation in betas from years past.)
Maybe I will start disabling that checkbox... (I am strong believer in using defaults unless I have really good reasons. This could be one. 😉 )