Hello,
We're building a package and the installation part is running fine. We're working on the customization of the app's config file after the install and hitting a few problems..
The config file is neither a .ini nor is it in the registry. It's a text file we edit via a vbscript.
What we need is for an IP address to be specified somewhere during the install to be passed to the customization script. There's no network connection, we just need the text string representing the server's address.
So far we've found we could use an inline script to popup an InputBox and set a property...
1. Is there a better way to do it ?
2. Could this still be used as we want during a silent install ?
If 2. is NO, what other ways could be pass a value to the installation process so that it's passed to the customization script running at the end ?
Thanks for any pointers...
Suggested Articles
Hello,
2. Yes, the InputBox will also be displayed during a silent install.
Regards,
Denis
1. No, this is the best solution.So far we've found we could use an inline script to popup an InputBox and set a property...
1. Is there a better way to do it ?
2. Could this still be used as we want during a silent install ?
2. Yes, the InputBox will also be displayed during a silent install.
Regards,
Denis
Cool, thanks for the reply.. Of course we're looking forward to customizable GUI panels so we can do this without so much scripting in the next versions 
Regarding the silent install, we're planning to test if the property has a value before executing the inputbox part or not.. this way running the installer from the command line with PROP=VALUE we shouldnt see anything and be really 'silent'..
wish us luck
Regarding the silent install, we're planning to test if the property has a value before executing the inputbox part or not.. this way running the installer from the command line with PROP=VALUE we shouldnt see anything and be really 'silent'..
wish us luck
Hello,
It is very easy to prevent the InputBox from displaying by testing the value of the property.
Basically, there are two methods for achieving this:
1. Set the name of the property as the Execution Condition for your script in the Custom Actions page.
2. Test if the property has a value before invoking the InputBox inside the script itself. This is useful if the script needs to perform other tasks as well.
However, should you encounter any problems, please let me know.
Good luck!
Regards,
Denis
It is very easy to prevent the InputBox from displaying by testing the value of the property.
Basically, there are two methods for achieving this:
1. Set the name of the property as the Execution Condition for your script in the Custom Actions page.
2. Test if the property has a value before invoking the InputBox inside the script itself. This is useful if the script needs to perform other tasks as well.
However, should you encounter any problems, please let me know.
Good luck!
Regards,
Denis