Installer or Executable for updated code

[SB_123]

I am developing the LabVIEW program on a single PC and then creating an installer to run it on a separate PC. For every update, do I need to run the installer every time there is an update? or I can simply use the executable for new updates as the PC already has LabVIEW Run-Time Engine (installed during the first run of the installer file).

[jcarmody]

>>  I can simply use the executable for new updates

You can do this.

<edit> My company restricts access to the Program File directories, so I always make sure to check this in the installer build spec:

</edit>

[billko]

I rebuild the installer and update the installer version.  The installer version shows up in "Add or remove programs" so you can keep track of which version is installed where.  Additionally, it will install any updated files you might have, like config files, for instance.  But it is also smart enough not to install stuff that is already installed.

[crossrulz]

When in integration/debug mode of the development cycle, I just replace the executable.  When time for a release, use the installer to make sure you have the latest.

[RTSLVU]

---

@crossrulz wrote:

When in integration/debug mode of the development cycle, I just replace the executable.  When time for a release, use the installer to make sure you have the latest.

---

Same here...

[RTSLVU]

---

@jcarmody wrote:

<edit> My company restricts access to the Program File directories, so I always make sure to check this in the installer build spec:

That's kind of silly, don't they understand that you can run an executable from any directory? Naming a directory "Program Files" is just a convince, and blocking access to that directory only provides a false sense of security. 

If they were serious they would use something like "Carbon Black" that literally blocks any executable that was not preapproved to run like my company does.   

I can't run the programs I write on my company laptop once compile them into an executable. 

[jcarmody]

>> That's kind of silly,

😄 We have job openings, too!