Hello,
It is theoretically possible to achieve the same effect in a Professional project, mind you it's not the recommended (or the 'right') way to do it.
Let's say you have the following structure:
Code: Select all
- first time install installs:
- application.exe
- file1.txt
- file2.txt
- file3.txt
- then you update your application to version 1.1 and the changed files were application.exe and file2.exe in that version.
Your 'update installer' (if we can call it that) backs up application.exe and file2.txt in the already installed application (using a custom action you will have to create), then installs the updated application.exe and file2.exe. But the update installer must be seen by Windows Installer as a totally new and separate product for this to work (new Upgrade Code and new Product Code). You can then uninstall the update and the 'update installer' should remove the application.exe and file2.exe automatically, then restore the backed up application.exe and file2.txt through some custom action.
But it's not a pretty workaround, and you must account for the case where the user uninstalls the main installation after the update has been installed. What should happen with the update in that case? Should it be uninstalled too?
Best regards,
Gabriel
FOLLOW US
Get the latest news in Application Packaging