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
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: IsCmdBld Prerequisites in single Setup.exe
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
‎May 02, 2012
05:41 AM
IsCmdBld Prerequisites in single Setup.exe
Hello,
I have a release configuration web style, which puts the whole installation files into one setup.exe, including the prerequisites. This works fine building it from inside InstallShield. Now I want to build the same single setup.exe automated, using IsCmdBuild. In this case I get the setup.exe and an extra folder "ISSetupPrerequisites", where the prerequisites are located, although I am using the -c COMP switch. Does anyone know a way to avoid this extra folder?
Gint
I have a release configuration web style, which puts the whole installation files into one setup.exe, including the prerequisites. This works fine building it from inside InstallShield. Now I want to build the same single setup.exe automated, using IsCmdBuild. In this case I get the setup.exe and an extra folder "ISSetupPrerequisites", where the prerequisites are located, although I am using the -c COMP switch. Does anyone know a way to avoid this extra folder?
Gint
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 02, 2012
06:31 AM
Are you trying to build a release which is already created? In that case, use -r to specify the release name. Do not use -c.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 02, 2012
08:37 AM
Thnak you for your suggestion J_anitha, but that does not work. Yes, I am trying to build a release which is already created, but when I do not set the -c switch, I get even uncompressed files.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 02, 2012
12:19 PM
Make sure that Extract From Setup.exe is selected for the InstallShield Prerequisites Location setting in the Releases view.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 03, 2012
01:12 AM
Extract From Setup.exe is selected, DebbieL, otherwise I wouldn't get a single exe when building from inside InstallShield.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2012
02:26 PM
Please try a command line such as the following:
iscmdbld.exe -p "C:\PathToProject\Project.ism" -a "Product Configuration Name" -r "Release Name"
Where Product Configuration Name is the name of the product configuration in the Releases view that contains the release you want to build, and Release Name is the name of the release in the Releases view you want to build. Note that both of these are case sensitive, so if the names don't match exactly you will get a new release with default settings (which is uncompressed).
iscmdbld.exe -p "C:\PathToProject\Project.ism" -a "Product Configuration Name" -r "Release Name"
Where Product Configuration Name is the name of the product configuration in the Releases view that contains the release you want to build, and Release Name is the name of the release in the Releases view you want to build. Note that both of these are case sensitive, so if the names don't match exactly you will get a new release with default settings (which is uncompressed).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 08, 2012
02:08 AM
joshstechnij's solution worked, thank you very much! I did not use the a-switch, that's why I got a new uncompressed release.