7 replies to this topic

[Alny]

I need to save some data from previous installed version (for example list of users), and insert them into new (installed) version.
Of course I want to do it during new version installation. But problem is that standard Custom Action "RemoveExistingProducts" in InstallExecuteSequence table goes before any user-defined custom action, and I can't save previous data in my custom actions, because they are already uninstalled.
When I move RemoveExistingProducts after InstallFinalize action, as recomended on Microsoft Site, it uninstalls (deletes) just installed application files .
When I put RemoveExistingProducts just before InstallFinalize I get an error

[Stefan Krueger]

Why don't you sequence your custom action before removeExistingProducts?

[Alny]

Because I got an error

[Stefan Krueger]

I didn't talk about moving thr removeExistingProducts action.

[Alny]

Yes, but when removeExistingProducts located at standart place: between InstallValidate and InstallInitialize, and i sequence custom actions before RemoveExistingProducts, I get another error

[Stefan Krueger]

Make sure your custom action is of type Immediate, not Deferred.

[Alny]

Thanks. Тhe problem indeed was related to custom action type (it was Deferred, not Immediate)

[Rimidalv Veigro]

I have the same problem.
But if I run the installer with a non-admin user, the Immediate action cannot modify registry keys. Only actions in system context can do that. Immediate actions in system context are not supported.
I have to puct the actions in that order:

.....
InstallInitialize
MyCustomAction
RemoveExistingProducts
......

MyCustomAction changes some registry keys.