This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Create Silent Sub-installers
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 13, 2011
10:21 AM
Create Silent Sub-installers
Hello,
I would like to know how to silence sub-installers within an InstallAnywhere installer. I have inherited an InstallShield project that runs several (outside, non-InstallShield) installers silently using .iss response files. Can something similar be done in InstallAnywhere?
Thanks
I would like to know how to silence sub-installers within an InstallAnywhere installer. I have inherited an InstallShield project that runs several (outside, non-InstallShield) installers silently using .iss response files. Can something similar be done in InstallAnywhere?
Thanks
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 13, 2011
11:59 AM
Okay, going on what I can glean from the user guide and forums, I have tried the following, which does not work:
I created an installer that puts the sub-installers on the user's computer (just in the install folder for this test).
I checked Always Generate Response File.
I use the Execute Target File action to run the installers.
After I run the installer I have created, I grab the response file, and put that into the installer, and deposit into the user's install folder.
I change execute Execute Target File action to include the following in the command line edit box: $EXECUTE_FILE_TARGET$ -f $IA_PROJECT_DIR$\installer.properties
Sorry if any or all of the above is laughably wrong, but I appear to be lacking in one or more pieces of fundamental InstallAnywhere knowledge that would allow me to get past this roadblock.
I created an installer that puts the sub-installers on the user's computer (just in the install folder for this test).
I checked Always Generate Response File.
I use the Execute Target File action to run the installers.
After I run the installer I have created, I grab the response file, and put that into the installer, and deposit into the user's install folder.
I change execute Execute Target File action to include the following in the command line edit box: $EXECUTE_FILE_TARGET$ -f $IA_PROJECT_DIR$\installer.properties
Sorry if any or all of the above is laughably wrong, but I appear to be lacking in one or more pieces of fundamental InstallAnywhere knowledge that would allow me to get past this roadblock.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 27, 2011
09:30 AM
Hi william01,
The configuration your doing here seems to be pretty much correct.
Another way InstallAnywhere installs sub-installer from Parent Project is Merge Modules.
Lets us know in-case of any difficulty you face.
Thanks,
Madhav Pai
InstallAnywhere Engineering,
Flexera Software
The configuration your doing here seems to be pretty much correct.
Another way InstallAnywhere installs sub-installer from Parent Project is Merge Modules.
Lets us know in-case of any difficulty you face.
Thanks,
Madhav Pai
InstallAnywhere Engineering,
Flexera Software
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 30, 2011
11:49 AM
william01 wrote:
Okay, going on what I can glean from the user guide and forums, I have tried the following, which does not work:
I created an installer that puts the sub-installers on the user's computer (just in the install folder for this test).
I checked Always Generate Response File.
I use the Execute Target File action to run the installers.
After I run the installer I have created, I grab the response file, and put that into the installer, and deposit into the user's install folder.
I change execute Execute Target File action to include the following in the command line edit box: $EXECUTE_FILE_TARGET$ -f $IA_PROJECT_DIR$\installer.properties
Sorry if any or all of the above is laughably wrong, but I appear to be lacking in one or more pieces of fundamental InstallAnywhere knowledge that would allow me to get past this roadblock.
This seems liek you have generated the response file for the parent installer rather than the sub installer. You should have a prop file made for the sub-installer and name it
That might help.