10-23-2017 09:24 AM
When I ran the 2017 .exe on a 2015 run-time machine, it spewed out an error. Is it necessary to install 2017 (32 and 64 bit) run-time on the machine to make 2017 .exe work? Is it possible to downgrade the 2017 executable to 2015 version?
Solved! Go to Solution.
10-23-2017 09:31 AM - edited 10-23-2017 09:32 AM
Hi kaivan,
yes, you need the 2017 runtime to run the EXE created with LV2017. (You even need to check for bitness 32/64…)
No, you cannot downgrade the 2017 EXE directly. You need to downgrade the VIs/project used to create this EXE to LV2015 and then you need to build the EXE using your LV2015 environment.
10-23-2017 09:40 AM
Yes that makes sense. Could you elaborate on how to downgrade the VIs/project to LV2015?
Thank you for responding,
Kaivan
10-23-2017 09:43 AM
10-23-2017 09:54 AM
I followed those steps, but could I could not find an option to downgrade it to 2015. The latest I could do it to was LV 2012. I have attached the screenshots.
10-23-2017 10:41 AM - edited 10-23-2017 10:42 AM
See where it says "LabVIEW Version" above a drop-down that says "17.0"? Change that to "15.0". Or are you saying that "15.0" isn't an option in that drop-down list?
10-23-2017 10:41 AM
Click in the listbox that is labeled LabVIEW Version and currently shows LV 2017.
10-23-2017 10:45 AM - edited 10-23-2017 10:46 AM
@artetile
There is an option 15.0.
But I am a bit confused. There is no LV 2015? Should there be something like that?
Or should I just select version 15.0 and that should convert it to LV 2015?
10-23-2017 10:45 AM - edited 10-23-2017 10:46 AM
@Ravens Fans
Oh so version 17 means LV 2017?
That means version 15 should be LV 2015, right?
10-23-2017 10:51 AM - edited 10-23-2017 10:51 AM
That's correct, just like if you choose "About" from the "Help" menu it'll show you that LabVIEW 2017 is version 17.0 (or 17.0f2 if you're current on patches), LabVIEW 2015 is version 15.0.
Aaron T.