My application writes all files to a single folder, c:\mycompanyname\. When the installer does an upgrade from an old version to the new, it erases everything in c:\mycompanyname\ and writes everything into it. That's fine and good behavior, however, there is data in that folder I need to have saved (as well as a MySQL database residing in there), or backed up (and then put back) at the start of the upgrade process.
Is there a way to run a script before the file-changing aspects of the installer, so I can put the commands I need the installer to run in before it destructively erases the data? I know I can get around this problem by having my users manually run the backup script before I have them run the installer program, but that seems counter-productive.
FOLLOW US
Get the latest news in Application Packaging