Bob Arnson wrote: > Peter G. Sakhno wrote: >> 1) I have set of files each in a separate component. And some of those >> files are not uninstalled. In MSIEXEC log I found following records for >> those components: >> “MSI (s) (C8:9C) [...]: Component: ViewerExeComponent; Installed: Local; >> Request: Absent; Action: Null”. As I can guess MSIEXEC generates no >> action for that component. And everything starts to work perfect if I >> change the name of the file, or name of installation directory or even >> add this file to the component that is uninstalled correctly. And I need >> to keep original file and directory names and current components. Why >> MSIEXEC can skip these files during un-installation? >> > Usually it's because MSI thinks another product is using those > components. Search the verbose log for other mentions of the component > id or its guid. Yes, seems MSI really thinks those components are pinned... I found ComponentUnregister with PreviouslyPinned=1, but I did not find any mentions about those components in registry. So, why MSI can think they are pinned? >> 2) I need to perform a custom action at final step of un-installation. >> What properties tell that current MSI session is UNINSTALLATION of the >> product? I write following code: >> <InstallExecuteSequence> >> <Custom Action="OnUninstall" After="InstallFinalize">Installed AND >> REMOVE="ALL"</Custom> >> </InstallExecuteSequence>. >> I t works fine, but I am not sure if this is a correct check. >> > That's fine. > Best regards, Peter G. Sakhno C-MAP RUSSIA Ltd http://www.c-map.ru/
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
