Our software wants to write information to the .INI file that is used to describe and control its own invocation. That file is normally in the Windows directory (a legacy of the way MS said to do things in the past), so it can't be written to by our program when that program is running under a limited account on Vista.
The information we need to write into the .INI file has to be determined dynamically. (It has to include the path to a 3rd-party product with which we are interfacing.) The name of the .INI file can also vary (to support multiple installs of our app, each has its own .INI file).
Our running software could easily put a file in a writeable location (e.g. Application Data\{current user}\companyname\) containing the name of the .INI file and the data that needs to be written to the .INI file. It could then run an MSI that does the work by reading that file to find out what to do, then writing to the appropriate file. I want an easy way to build that MSI.
It seems that using a Javascript / VBScript file would be the best way to do this. Are there any examples of doing such things? Does anyone have any hints / tips / gotchas to tell me about? Am I right that this would require the not-free version of the software?
Thanks for any input.
FOLLOW US
Get the latest news in Application Packaging