Bob Arnson wrote: check out the PatchFiles action to see what MSI actually does.
Thanks Bob. I couldn't seem to find a PatchFiles action in the log though, so perhaps that is the problem. Using Orca I applied my patch to the MSI and I don't see a PatchFiles in the InstallExecuteSequence table either. What would cause this not to be included? Do I need to explicitly sequence this in my original or update MSI? Thanks, Shawn On Wed, Jun 3, 2009 at 9:54 PM, Bob Arnson <b...@joyofsetup.com> wrote: > Shawn Dwyer wrote: > >> below. In the example, NewFile.exe and NewFile.exe.config are both in the >> same Component, where NewFile.exe is the keyfile being upgraded from >> 3.0.37 >> to 3.0.38, and NewFile.exe.config has new content but obviously no version >> number. The results I am seeing is that NewFile.exe.config is replaced by >> the patch, but NewFile.exe remains at 3.0.37. If you're reading the >> attached log, XPIMAppServiceHost.exe.config is the only file that is >> updated >> by the patch. Is it just a coincidence that only non-versioned files are >> updated? >> >> > > Probably. The logging you provided looks right -- check out the PatchFiles > action to see what MSI actually does. > > -- > sig://boB > http://joyofsetup.com/ > > > ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
