App Builder: How to evaluate destination path?

[Klaus_M]

I need to add individual *.ini files to a LabVIEW application program, but should always use the same build (installer volume) plus this individual *.ini file.

This is needed for individual customer settings, that should be automatically copied to the destination during the installation.

This could be solved ba adding the destination path as command line argument to run an executable (a batch file e.g.) at the end of installation. This executable should then copy the *.ini file from the installation media to the application program destination.

I'd like to define the call in Application Builder - Installer - Properties - Advanced [] Run executable

Is there a variable available? 

How can it be forwarded in the command line?

Thanks for any tip!

Klaus

[Jörn]

Maybe my thoughts can help you:  

As far as I understood you produce customised installer volumes. So you don't really need the exact names of files in the ini-directory of the installer volume. Just copy all contents.

For the destination you can use the respective variables of the operation system.

Regards

[Klaus_M]

Jörn

Thanks for your answer.

I believe this is not a solution for my problem. I try to explain my problem.

My customers are OEM's and should receive the following from me:

- An Installer with standard Program, built with App Builder (all files are packed now).

- An OEM.ini file to add informations and special settings. (i.e. this happens after the application build).

--> The OEM edits the OEM.ini and copies all on an USB stick.

Now the OEM's enduser receives an USB stick from where he wants to run setup.exe. This should install the application and copy the individual OEM.ini File into the program directory.

It's clear, that  the LabVIEW setup.exe could be called by a batch file, that afterwards copies the OEM.ini File. But where did the enduser install his software?

It seems to me, that my question has not been clear enough.

The questions remain:

In the Application Builder (refer to my first post):

Is there a variable available representing the destination path? 

How can it be forwarded in the command line for the executable running after setup?

 Regards

Klaus

[Klaus_M · Accepted solution]

Here is the solution:

http://zone.ni.com/reference/en-XX/help/371361E-01/lvdialog/adv_installer_settings_db/

This text is also available in the Application Builder help 😉

Sorry for the noise!

Klaus