Hi Zsolt,
I tested your both scenario and here is what I noticed:
Scenario 2:
Do everything in the exact same way like in Scenario 1 with one difference: PRODUCT_2 has to be a MAJOR update with different product code.
After Step 5 (uninstallation) our FW rules are not removed by the installer, they are still in the incoming rules list -> this is the problem, because we don't want to leave our garbage on the customer's PC.
Could you please also check the uninstallation logfiles for each scenario? In minor_log.log you will see some AI_FwRemove actions which are running for each individual rule. Those lines are missing in major_log.log.
The firewall rules were removed as expected during the uninstall. Furthermore, I noticed that both major and minor log files contain similar lines about the "AI_FwUninstall" custom action.
Do you reproduce the problem on multiple clean machines? If so, can you please send me a sample project that reproduces the problem?
For example I have a feature called TheWebAccess and a firewall rule for it with this install condition:
"(&TheWebAccess=3 OR !TheWebAccess=3)"
Note: AI_FWUninstall condition in table editor has not been overwritten yet, the product that I use for testing is one of our previous releases without an FW related changes added to it.
After I install the product on a PC, go to Programs and Features and remove the feature called TheWebAccess, I´d expect the belonging FW rule to be removed. But unfortunately it´s not being removed.
Please note that the uninstall firewall rules custom action is executed only on a full uninstall of the package, not on the removal of individual features.
If you want to achieve this for a feature, you can go in the "InstallExecuteSequence" table from the "Table Editor" page and set the following condition for the "AI_FwUninstall" row:
(VersionNT >= 501) AND (REMOVE="ALL") OR ((&TheWebAccess = 2) AND (!TheWebAccess = 3))
Let me know if this helped.
Best regards,
Eusebiu
FOLLOW US
Get the latest news in Application Packaging