In article <[EMAIL PROTECTED]>,
Dan Hoeger <[EMAIL PROTECTED]> writes:
> The issue is that one of the custom actions is depending on a property
> that i s only available during a UI install and when an upgrade is
> performed the previ ous install is removed silently and the custom action
> fails because this value is not set.
You can work around this by applying a patch to the existing product
before you upgrade it. The patch corrects the problem in the previous
release before you upgrade it so that the upgrade proceeds properly.
In your case, you can add code to have the property set correctly or
you can adjust the custom action code itself or you can conditionalize
the custom action not to run during an upgrade.
If you have a bootstrapper, you can add code to your bootstrapper to
ensure that the patch is applied before upgrading, or you can create
manual instructions for applying the patch first. I did it through
the bootstrapper that we already had so that I could guarantee the
patch was applied if it wasn't already present. This isn't that hard
to do, but its quite a bit of work if you don't already have a
bootstrapper.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
