Silent install is heavily used in my installation. and if there's an error messagebox popups that's not defined in my iss file (silent installation file). I'll get a negative result code in my silent install log.
Here's a common mistake/error I want to trap: 1. if I use a string table entry name that was misspelled, it will throw an error telling me that there no such entry in my string table
example. I have MSG_STATUS in my table entry and I misspelled it in my installscript code - @MSG_STATUSS <-- this will throw a message box and my code will immediately goto OnAbort(). Then my silent install will return a negative result.
How can I handle this. I want to trap it. try/catch block does not work.
InstallShield 2009 added a build error for a missing string-table entry as you describe it; for InstallShield 2008 and earlier, perhaps use LoadStringFromStringTable instead of the @STRING_ID syntax?
