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: How to get standalone build to stop on first error
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
‎Dec 10, 2014
07:16 AM
How to get standalone build to stop on first error
I am looking for the setting that allows the standalone build to stop on first error.
For instance our current build is broken in that it is missing a required file. The standalone build reports the missing file as an error but still continues to build and returns 0 (zero) as the return code from setup. I want the build to stop immediately on the first error.
I looked at the IDE and it has an option inside the tools > option to "Stop build process when first error is encountered". I checked the registry to see if there is an equivalent value found there but did not find anything obvious under HKLM or HKCU.
For instance our current build is broken in that it is missing a required file. The standalone build reports the missing file as an error but still continues to build and returns 0 (zero) as the return code from setup. I want the build to stop immediately on the first error.
I looked at the IDE and it has an option inside the tools > option to "Stop build process when first error is encountered". I checked the registry to see if there is an equivalent value found there but did not find anything obvious under HKLM or HKCU.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 10, 2014
07:29 AM
Doh, I forgot to refresh my registry view in my development environment. I found the registry key. 😛
For others that may come across my entry, try the following:
[CODE][HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield\20.0\Professional\Project Settings]
"StopAtFirstErr"=dword:00000001[/CODE]
Be sure to use the correct version value for the version you are updating, e.g, 20.0 for IS2013, 21.0 for IS2014, etc.
EDIT: Note that I have not tested this yet, but I suspect that this will allow for the correct behavior. For the IDE, the settings are made in HKCU, but for the standalone build I cannot find an InstallShield key at all, so I just transposed them to HKLM similar to what we do to set the merge module path and prerequisite path in the registry for the standalone build.
For others that may come across my entry, try the following:
[CODE][HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield\20.0\Professional\Project Settings]
"StopAtFirstErr"=dword:00000001[/CODE]
Be sure to use the correct version value for the version you are updating, e.g, 20.0 for IS2013, 21.0 for IS2014, etc.
EDIT: Note that I have not tested this yet, but I suspect that this will allow for the correct behavior. For the IDE, the settings are made in HKCU, but for the standalone build I cannot find an InstallShield key at all, so I just transposed them to HKLM similar to what we do to set the merge module path and prerequisite path in the registry for the standalone build.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 10, 2014
03:12 PM
You could also consider passing the -x parameter to iscmdbld.exe; that's the documented method. 🙂
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 11, 2014
09:08 AM
MichaelU wrote:
You could also consider passing the -x parameter to iscmdbld.exe; that's the documented method. 🙂
Ha! I had read through the parameters and completely missed that too.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)