Hi John, Thanks for the reply.The upgrade used to work well previously..Also i am sure, that the changes that was done later on, does not break the upgrade.
I already have your suggested approach #2 implemented when the major upgrade was implemented. I have a custom action which takes a backup of config files before the 'RemoveExistingProducts'. There is another custom action 'RestoreConfiguration' for performing the restore, after the config files are installed and before InstallFinalize. I am getting the FileNotFoundException during this custom action only... As posted earlier, I feel while upgrade, a cached version of installer is being used, since some of the changes i made to debug the issue( for e.g. added extra logging in C# custom action or removing the custom actions altogether) is not getting reflected. I confirmed this, looking at the installer log. Any thoughts? Thanks, Arvind P.S : I am planning to test the upgrade on a clean machine. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Upgrade-Issue-tp7596837p7596839.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
