Select which Runtime to use with "future versions allowed" property.

[VolodymyrM]

I have built applications in 2019 SP1 x64 development system with property

• Allow future versions of the LabVIEW Runtime to run this application—Enables this application to run with future versions of the LabVIEW Run-Time Engine. You can disable this option to bind a build specification to a specific version of LabVIEW. Disabling this option prevents any changes to the performance profiles and helps you avoid unexpected problems resulting from compiler upgrades.

Now when Runtime 2020 is available new users start to use Runtime 2020 and I have "unexpected problems". Question is:
How can I force the built application to use specifically 2019 Runtime when both Runtime 2020 and 2019 are installed on the target system?

P.S. Problem disappears when built from 2020 Development system without the use of Fast file format. But still, there's a need to support previous versions of app.

Thanks, Volodymyr

[VolodymyrM]

Somehow problem with UI events when using 2020 Runtime was related to:

• Use fast file format—Saves the stand-alone applications (EXE) or shared libraries (DLL) in a format that loads faster. To use the fast file format, ensure that the Enable debugging checkbox on the Advanced page does not contain a checkmark.
  
  The fast file format does not support applications that contain 3D graphs. When you enable the fast file format, LabVIEW does not use the Application Builder object cache. Therefore, stand-alone applications and shared libraries may take longer to build.

Debug option was disabled and 3D graphs aren't present in app.

[ShockHouse]

In reponse to "How can I force the built application to use specifically 2019 Runtime when both Runtime 2020 and 2019 are installed on the target system?"

Just uncheck the "allow future versions to run this application". When it's unchecked it forces the .exe to run in whatever version it was built in. So if you build in 2019, and have that unchecked, the .exe will always run in 2019.

[MaximeR]

I have suggested the idea here

Add ability to select which version of LabVIEW Runtime is compatible with executable - NI Community

And added this one this morning which is linked :

Add ability to disable "Allow future versions of the LabVIEW Runtime" for Real Time application - NI...

I'm happy that I'm not the only one but unhappy of the behavior of LabVIEW and NI.

Best regards

[billko]

I think this is a bane for older executables because they will try to run in the latest LVRT, I believe even if you have the LVRT for the executable installed.  Someone had a nasty surprise after upgrading LabVIEW, where suddenly an old executable no longer worked.