LV2009 EXE - remote update

[MogaRaghu]

Have built an EXE_Ver.1.0 with LV2009 and deployed on the client PC in remote location. ( remote = 12 hours travel by flight !) The machine has the LV2009 Full development pack installed on it.

There were some code changes to be done. Due to some license issues, I had to save the LV2009 code into LV8.6 and I now have built the EXE_Ver1.1 in LV8.6.

If I have to send the EXE_Ver1.1 to the client, is it enough if I just send the EXE file or am I to enclose some other files which get created as part of the build process ? Thanks for any tips.

[altenbach]

They probably need the 8.6 runtime engine, freely downloadable from NI (the large 100+MB file, not the short version).... or you could built an installer and include it.

[MogaRaghu]

Since a later version of LV opens a VI coded in previous version, I thought the same logic will apply with EXE files. As I have built the EXE with LV8.6 and the client PC has LV2009 FDS installed on it, I thought the LV2009 RTE will handle my 8.6 EXE without complaints. But looks like my understanding is wrong - to run a EXE built with Version X, you need the exact Version X run time ?

Building an installer with the RTE included will of course obviate the problem. But will open a new problem of laaaarge file upload. Maybe I will ask the client to download and install the required RTE and send only the EXE ??

[altenbach]

---

Raghunathan wrote:

to run a EXE built with Version X, you need the exact Version X run time ?

---

Yes, this is my understanding.

[rolfk · Accepted solution]

---

Raghunathan wrote:

Since a later version of LV opens a VI coded in previous version, I thought the same logic will apply with EXE files. As I have built the EXE with LV8.6 and the client PC has LV2009 FDS installed on it, I thought the LV2009 RTE will handle my 8.6 EXE without complaints. But looks like my understanding is wrong - to run a EXE built with Version X, you need the exact Version X run time ?

---

Exactly! The ability to read previous versions also requires the VI code to be recompiled after being loaded in. Both the backwards version loading code as well as the compiler are not part of the runtime engine, so it can not open VIs compiled for any other version nor platform than its own.

Message Edited by rolfk on 11-22-2009 01:39 PM

[MogaRaghu]

Yes thats exactly the information that I was looking for.

Thanks for all those took time to respond.