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
- :
- Why is DEBUG always enabled for custom actions?
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
Jun 27, 2013
10:19 AM
Why is DEBUG always enabled for custom actions?
I have Basic MSI project with a number of custom actions written in InstallScript. Every time I run the setup, the InstallScript debug window opens at the first line of each function. (So DEBUG and RUN SETUP are behaving the same). I have no breakpoints set.
I have searched exhausively for ways to disable DEBUG, but come up with nothing. I tried creating a very simple project with just a few files and one (immediate) custom action that does nothing other than set a variable, yet the debug window still opens.
As no one else seems to be complaining about this behavior, I even reinstalled IS 12 with SP2, but the DEBUG window still opens.
This is driving me crazy. How can I turn this behavior off?
I have searched exhausively for ways to disable DEBUG, but come up with nothing. I tried creating a very simple project with just a few files and one (immediate) custom action that does nothing other than set a variable, yet the debug window still opens.
As no one else seems to be complaining about this behavior, I even reinstalled IS 12 with SP2, but the DEBUG window still opens.
This is driving me crazy. How can I turn this behavior off?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 27, 2013
11:52 AM
I have since discovered that the registry setting DebugISCustomActions in HKCU\Software\InstallShield\ISEngine 12.0 was set to 1. I have changed it to 0 and the problem went away.
