Is there a way to debug an installer executable file created with a generic installer screen?
I created a Windows executable with some custom actions and some UI stuff.
I ran into strange behavior with installability.
I've tried probing through the code and cleaning up the installer as much as possible, but I haven't found any idea why the strange behavior is available.
So I wanted to debug the installer at every point in the code execution in a custom activity for which I was trying to write down the values the logger requires. Unfortunately, my registrar will be created after installation, after which I will not be able to start it up again.
So, can anyone suggest to debug it at runtime installable?
source to share
I tried but couldn't get a debugger working with Installshield universal.
My workaround was to add a lot of debug messages and use VMware. Install VMware and create a test machine as a virtual server. I configured a virtual server with all the prerequisites, rebooted it and then took a snapshot.
After the snapshot, I ran the install script, waited for errors and log files. I would then use VMware's "return to snapshot" feature to go back to a clean test server instance and start investigating error messages from the logs.
source to share