I unfortunately have another issue I do not understand.
We have a configuration file, Configs.xml, that is installed with our product. The file is associated to the Configs.xml component and is configured to never overwrite an existing file. There is also a Modify XML action which changes one of the configuration values in Configs.xml based on data entered into the installation wizard by the user. This action is associated with a component which is always installed to ensure it always runs.
All of that works fine.
During the uninstall process, there is an option to remove all configuration data. This option sets the property REMOVE_CONFIGURATION to 1 if checked. There is also a Remove File operation, called Configs.xml, and set its condition to REMOVE_CONFIGURATION="1". The Remove File operation is associated with a component that is always removed to ensure it always runs.
Here are some screenshots showing the setup in Advanced Installer:
The Remove File settings:
According to the log captured during uninstall, the REMOVE_CONFIGURATION property is set to 1, but the Configs.xml file is NOT removed. Other Remove File operations execute as expected:
Code: Select all
Action start 17:50:11: ExecuteAction.
...
MSI (s) (9C:B0) [17:50:11:740]: PROPERTY CHANGE: Modifying REMOVE_CONFIGURATION property. Its current value is '0'. Its new value: '1'.
...
MSI (s) (9C:B0) [17:50:19:254]: Executing op: SetTargetFolder(Folder=C:\Program Files (x86)\CommSys\ConnectCIC\)
MSI (s) (9C:B0) [17:50:19:254]: Executing op: FileRemove(,FileName=request-response.xsl,,)
MSI (s) (9C:B0) [17:50:19:254]: Executing op: FileRemove(,FileName=CommonFunctions.vbs,,)
MSI (s) (9C:B0) [17:50:19:254]: Executing op: ProgressTotal(Total=564,Type=1,ByteEquivalent=175000)