Just an update on this. I tried changing the Component GUID, but realized that that won't work, because the files still target the same location, so I get the same error. That is, it's not looking up the Component GUID for determining if the component is pre-existing, but rather the destination itself.
Any suggestions on how to cleanly get around this issue? --Quinton > I found a problem where when we do a major update when a component in > the newer version has a key file with an older version than the version > its updating. The problem is that the component gets rejected because "a > higher versioned keyfile exists", but then gets uninstalled by the major > update, so in the end no version of the component exists. This behavior > seems incorrect, since my application is the only one that uses this > component (although perhaps Windows Installer can't know that). > > What is the proper way to work around this? I'm thinking of just > changing the component ID. ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
