@WyrdFish, Thanks for the reply.
As MSI won't rewrite the unversioned file if it is modified, I have taken the following approach as a workaround. During install, my custom action writes some valus to web.config. During upgrade, installer wouldn't replace this web.config file as it is unversioned and modified. And inturn my custom action again writes the same values into the web.config file thus creating duplicated values in web.config. To solve this I am moving web.config to separate location and thus during upgrade, installer detects that the file is missing and copies that file. After that I will replace this new file with the existing one. Thus way I can avoid creation of duplicate keys with my custom action during upgrade. Do you think this might have caused the issue? @Pally Sandher I have tried using XmlConfig but in the following manner. When I am installing freshly, that package uses XmlFile, but I have replaced that with XmlConfig in upgradeable version package and tried upgrading. Still I got the same issue during uninstall. I will try using XmlConfig in both the packages and check if that works. Sainath A. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Uninstall-fails-after-upgrade-with-Error-25532-Failed-to-find-node-tp6522308p6524290.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
