Open topic with navigation

Locating the Source of the Error

InstallShield 2015 » InstallScript Debugger

The second step in the debugging process is to locate those parts of the setup that may be involved in the error.

If you have observed the symptoms yourself, you may already have a pretty good idea of where to look for the cause. Still, before you start debugging, it is wise to take a moment to think about the error and to identify obvious design or coding mistakes that could have caused it.

Even the simplest errors can often lead you to several different parts of your setup. For example, suppose the product name is not showing up in Sd dialogs. The error might be found where those dialogs are called. Or it may be that the initialization section fails to establish the product name by calling SdProductName. Or it could be that the call to SdProductName references an undefined string entry.

You probably would not need the debugger to handle that particular bug. But in cases where you would, you will make better use of the debugger if you have planned which parts of the script to trace and analyze for clues.