No this isn't anything in the GAC. The component in question is a piece
of a driver installed using the DifxAppExtension, and its absence wreaks
havoc on the attempt to install the driver, failing the major update.
However, the problem itself occurs prior to this, in that very early on
the installer decided not to update that component and it doesn't change
its mind even though we are removing remove the existing product.
Notice that I do have the RemoveExistingProducts action coming after
InstallInitialize:
<InstallExecuteSequence>
<RemoveExistingProducts After="InstallInitialize" />
</InstallExecuteSequence>
Not sure of the history for why that code is in my wxs file. What is the
suggested location for this action? I notice that the KB you reference
talks about moving RemoveExistingProducts to after InstallFinalize.
However, even if I move RemoveExistingProducts to the end, I'll still
have a problem with my installer not updating the component that I
wanted to totally replace. (The component is installed in a subfolder of
the product install path, and therefore not shared by other products.)
To summarize the core question, how can I change a keyfile in a
non-shared component to a previous version with a major upgrade? Perhaps
I need to change the key path for this component from the file to a
registry entry?
--Quinton
> Is this in the GAC? Sounds like that upgrade GAC problem.
http://support.microsoft.com/kb/905238
>
> Phil Wilson
------------------------------------------------------------------------------
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
