uninstall of legacy setups from inside an msi
hi there,
I'm facing the problem to remove 2 or more legacy setups (created by NSIS to be precise) before installing my MSI. I have searched the net for some time now but can't find a place to start from. The only thing I do know is that I can't use the upgrade table as it only works with installed GUIDs.
(NSIS creates something like this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BigNSISTest]
"DisplayName"="BigNSISTest (remove only)"
"UninstallString"="\"C:\\Program Files\\NSISTest\\BigNSISTest\\bt-uninst.exe\""
)
I'm facing the problem to remove 2 or more legacy setups (created by NSIS to be precise) before installing my MSI. I have searched the net for some time now but can't find a place to start from. The only thing I do know is that I can't use the upgrade table as it only works with installed GUIDs.
(NSIS creates something like this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BigNSISTest]
"DisplayName"="BigNSISTest (remove only)"
"UninstallString"="\"C:\\Program Files\\NSISTest\\BigNSISTest\\bt-uninst.exe\""
)
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
dunnpy
17 years ago
Llama,
You should be able to create a custom action in your MSI (or MST if it is a vendor MSI) that runs the uninstall string you've mentioned in your post.
There maybe a nice silent switch you can use - have a play with command line switches for the "bt-uninst.exe"
It may also be possible to use the original install .exe with switches to uninstall (/x or /uninstall maybe).
Hope this points you in right direction,
Dunnpy
You should be able to create a custom action in your MSI (or MST if it is a vendor MSI) that runs the uninstall string you've mentioned in your post.
There maybe a nice silent switch you can use - have a play with command line switches for the "bt-uninst.exe"
It may also be possible to use the original install .exe with switches to uninstall (/x or /uninstall maybe).
Hope this points you in right direction,
Dunnpy
Posted by:
jmcfadyen
17 years ago
use the appsearch table to search for a file / reg key that you know will exist when the app is installed.
when these are found you can set a property such as APPFOUND="xxxx"
then create a CA give it a condition of APPFOUND="xxxx" then use a silent uninstall command for the CA
when these are found you can set a property such as APPFOUND="xxxx"
then create a CA give it a condition of APPFOUND="xxxx" then use a silent uninstall command for the CA
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
