Hi Cosmin,
I didn't quite get to the real issue last time. Adding a dialog triggered it, but that turns out not to be the problem. Here is some more detail on how to reproduce.
0. verify product not installed
1. open installer project and compile both DefaultBuild and Build (this may not matter, but I'm creating a Setup.exe in addition to the MSI)
2. use Orca to collect the Package Code
3. run installer at the command line via Setup.exe or MyApp.msi (package is now installed)
4. run installer at the command line via Setup.exe or MyApp.msi a second time, observe maintenance dialog, CANCEL (product still installed, Package Code unchanged)
5. use Orca to verify the Package Code is unchanged
So far the behavior is exactly what I expected. I've run steps 2 and 3 with both Setup.exe and MyApp.msi in every permutation, with no problems whatsoever.
But then two unexpected things occur when running the project using the [ Run ] toolbar button: instead of seeing the maintenance dialog, the product is silently uninstalled and the original install dialog is displayed. If I cancel the silent uninstall on a second try, after finishing the cancel operation the maintenance dialog appears.
Shouldn't the Run button behave exactly the same way as a command line execution of the MSI or Setup.exe?
By the way, the Run button runs DefaultBuild, if I'm reading this page correctly
http://www.advancedinstaller.com/user-g ... jects.html. In any event, both Setup.exe and MyApp.msi work properly when run from the command line, so this may be an unimportant distinction.
Thanks,
Tim
FOLLOW US
Get the latest news in Application Packaging