4LetterState
5/21/2008 2:43:00 PM
Hello,
I have an install package that has a custom action for the Install and
Uninstall methods. Our application uses an Excel Add-in. During an uninstall,
if Excel is open, I hit error 1306 as that application has my Add-in file
locked. Instead of closing Excel, I choose to cancel the uninstall. At this
point, my .InstallState file has already been deleted because the CA runs
successfully before the REMOVEFILE action (where the 1306 error occurs).
So, on the 2nd attempt to uninstall (with Excel closed), I am unable to
remove the package because I have lost my .InstallState file and information.
The uninstall custom action fails as a result of missing state information.
I know how to correct the problem and get the package removed (MSIZAP).
But, I would really like to know if it is possible to retain that State
information until the very last moment in the uninstall. I have tried
re-ordering events in the InstallExecuteSequence, but I can't have the
Uninstall CA after the RemoveFiles action.
Any ideas?
Thanks,
Brenda