Updating main VI in executable...

[apok]

I have already installed a standalone executable to another computer, software/hardware is working fine....I now want to make a few changes to the Main VI.

• Do I need make another full install of the updated VI?
• Do I need to uninstall the standalone executable and start fresh?
• Can I just update the Main VI and build without the runtime engine and daqmx files already installed on the standalone computer?

your input is appreciated.....

[JÞB · Accepted solution]

---

@apok wrote:

I have already installed a standalone executable to another computer, software/hardware is working fine....I now want to make a few changes to the Main VI.

• Do I need make another full install of the updated VI?  Good idea if you want to distribute the new application to "Any Target"
• Do I need to uninstall the standalone executable and start fresh? No
• Can I just update the Main VI and build without the runtime engine and daqmx files already installed on the standalone computer? Yes,  but your new installer should see that the dependancies are already installed and skip the installation of those files

your input is appreciated.....

---

In summary, it is better practice to update the installer so that when you install a fresh copy the installer is clean.

[crossrulz]

As Jeff has stated, it is really best to make a new installer.  Personally, I just copy over a new executable when I am in the debug stage of EXE development.  But once a release hits, it HAS TO be a new installer.

[altenbach]

---

@apok wrote:

1. Do I need make another full install of the updated VI?
2. Do I need to uninstall the standalone executable and start fresh?
3. Can I just update the Main VI and build without the runtime engine and daqmx files already installed on the standalone computer?

your input is appreciated.....

---

To answer all your questions:

1. I don't know what you mean by "full install", but if you included the run time engine in an earlier install, you no longer need to include that. This makes the installer much smaller and faster to install.
2. No, all you need is to ensure that you keep the same upgrade code when building the installer. Than ensures that the old installation gets overwritten. (If you use a different code, you'll end up with both version installed).
3. The installer knows what parts are already installed and will automatically skip whatever does not need to be upgraded.