Installer builder not flexible enough

[awilliotAcutronic]

Hello

I use the installer builder to create an installer for my application, but it lacks some flexibility.

For example I would like that it installs some files only under certain conditions, such as existence of some files on the disk, or according to the value of a new tickbox/button in the installer.

What would be the easiest way to accomplish that?

I already thought at using a completely different installer builder, such as Inno Setup, but then I loose all the benefits of the LabVIEW installer builder such as runtime installers, LabVIEW API... 

[wiebe@CARYA]

---

@awilliotAcutronic wrote:

I already thought at using a completely different installer builder, such as Inno Setup, but then I use all the benefits of the LabVIEW installer builder such as runtime installers, LabVIEW API... 

---

I think a 3rd party installer is the usual solution. I've also seen installers being build in LabVIEW, so the LV exe is run after the installer is done. But it's a lot of work to make nice screens.

I think you normally a) add Inno installer to the LabVIEW installer, or b) add the LabVIEW installer to the Inno installer.

[Hooovahh]

Yup as much as I'd like it to be part of the builder process, I too use Inno setup and ISTool.

https://forums.ni.com/t5/LabVIEW/LabVIEW-installer-with-Inno-setup/m-p/3688270#M1037104

NI installers are quite intelligent for the most part.  If you run an NI installer that contains DAQmx, VISA, XNet, and the Run-time engine.  It will only install the components that aren't installed (or are installed but a different version)