cosmin wrote:Hi,
You can do this by using custom actions.
In the "Custom Actions" page, under "InstallExecuteSequence->InstallFinalize" you create a
Exe with working Dir custom action. You set "Asynchronous execution, do not wait for return" in the "Execution Properties" section and you set the "Full Path" to:
Note that
/qn will make the uninstall silent.
In the "Install" tree you create a
Launch File or Open URL custom action which will launch your application.
Regards,
cosmin
I am sorry, I do not understand what you mean.
You said that
In the "Custom Actions" page, under "InstallExecuteSequence->InstallFinalize"
But there is no "InstallFinalize" parameter anyway on the Custom Actions page. There is a "InstallExecuteSequence" folder. And under that folder there is a "uninstall", "Rollback", "Install" and "Commit" folder. But "InstallFinalize"? It's no way to be found.
And you said that
In the "Install" tree you create a Launch File or Open URL custom action which will launch your application.
I don't get this. I thought we have done what is needed in the "InstallExecuteSequence" and hence do not need to define a new action under "Install" folder tree?
The parameter to call the uninstallation program is, as you wrote:
I have a few questions here:
- How to specify the ProductCode? It's generated by Windows Installer and we usually don't know about it
- I read the help online, and found that one can replace ProductCode with the MSI path. I think it's easier to specify the MSI path rather than specifying the ProductCode for uninstallation purpose. This there anyway to get it?
FOLLOW US
Get the latest news in Application Packaging