I have a launch condition that prevents the installer continuing if a specific process is running. This works well during first install. However it does not seem to work when you go back in and modify the installation by adding a new feature etc.
This happens because launch conditions are not evaluated on maintenance (modify, repair, remove).
If you want all launch conditions to be evaluated on maintenance phase too you can go to Table Editor page, locate InstallUISequence and InstallExecuteSequence tables. Then in each of them locate the standard action "LaunchConditions",
then remove the current condition, i.e. NOT Installed, leaving the condition field empty.
NOTE, this till trigger evaluation of all launch conditions. So if for example you have a launch condition that checks for .NET 4.0 (which the user
had on the machine when he installed your application), this will be checked on uninstall too. So if the user uninstalls/downgrades the .NET platform
then he will not be able to uninstall your application.
FOLLOW US
Get the latest news in Application Packaging