I am developing an application for deployment as an executable
via an installation package. This application will need an
accompanying initialization file which will store user configurable
defaults (such as the root path to his data and other sundries).
I am familiar with the configuration (.ini) VIs, as well as the
application configuration file which resides in the same directory
as the executable (application_name.ini) which the run-time engine
automagically finds and loads.
The problem arises when I want to add a custom .ini file (or possibly
add custom entries in the application's existing file; can I do that?):
How do I identify the path to the file (which is the same as the path
to the executable)?
I have no final control over where the user installs his copy, so I
cannot use a hard-coded path to this file if I want this configuration
file to reside in the same place as the executable. I don't want the
application to not work simply because the user chooses to install it
somewhere other than the default place.
Bob
