There are a few project types in which to develop your installations in. One common project type is the Windows Installer or MSI. However, the project type I am developing in is the InstallScript project type. In order for an InstallScript project to run silently, you must first create a response file. The file directs the setup through the answers that a user would normally have to answer. The response file is a text file except that it has the ".iss" file type normally named "Setup.iss". I'm not going to explain more about this response file process. That is well documented in other places and can be easily found on the internet. What I want to talk about is how the setup can be created as one executable with the Setup.iss wrapped into it.
Here is the trick that I couldn't even find in Acresso's knowledge base. To wrap the response file into the installation so it isn't a separate file that you have to lug around with the setup executable, put it in the Support directory. More specifically, place it in the "Disk 1" subdirectory under the Support section. Simple, but effective. It took me 2 days to discover how to do this.
Thursday, September 17, 2009
Subscribe to:
Post Comments (Atom)
3 comments:
Does this approach still require that commandline arguments ( /s and /SMS) be used to run the setup exe silently?
Thank you!
Charlie
Wow! I guess I should check in more often. Yes. I use the /s switch to initialize silent mode. If you always want the install to run silent, with no human interaction, add the switch to 'Setup.exe' tab under the project's Release. If you do this, no command-line will need to be added to the executable.
Thanks to Garett! I got some exceptional news here. I think InstallAware is the better installer.
Post a Comment