Yes, quite helpful. This leads to the Patch "AllowRemoval" property,
which can be set to restrict uninstall:

<Patch AllowRemoval='no'...>

There is a quite detailed write up on this, which I'm sure everyone else
here is already familiar with. :-)

http://www.tramontana.co.hu/wix/lesson4.php



-----Original Message-----
From: Wendell Joost [mailto:wende...@gmail.com] 
Sent: Thursday, October 08, 2009 2:02 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX Installer that does not leave a trace
inAdd/Remove Programs

Was this not helpful?

http://msdn.microsoft.com/en-us/library/aa372102(VS.85).aspx

Wendell

-- 
"Some people come visit Europe and are really let down when they find
out it's not like a credit-card commercial; others really get into
meeting all the quirky people and careening along narrow mountain
roads in rickety cabs driven by suicidal, gap-toothed Carpathians. I
guess it's pretty obvious which one you are..." - Justin Crevier, May
'01


On Thu, Oct 8, 2009 at 6:15 AM, Thorpe, Alan <atho...@bottomline.com>
wrote:
> Perhaps I have not dug deeply enough into the patch aspects of WiX and
> MSI to figure this out yet, but... What is the correct method to
create
> an MSI using WiX that patches an existing product, but does not leave
an
> entry in the Add/Remove Programs list for users to attempt to
uninstall
> that patch?
>
>
>
> The situation is that the existing product has a proprietary
> registration process for plug-in components where it is easy to add or
> update modules, but next to impossible to roll back an updated module
to
> the previous version. Attempting to uninstall a patched module would,
in
> fact, likely remove or disable that component completely rather than
> revert it back to what was there before. I would prefer to patch what
is
> already there, but not offer users the option to uninstall the patch
via
> Add/Remove Programs and get themselves into deeper hot water. The
> "patch" would be reverted if necessary by re-running the product's own
> proprietary installer (not MSI).
>
>
>
>
>
>
------------------------------------------------------------------------
------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
your
> developing skills, take BlackBerry mobile applications to market and
stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

------------------------------------------------------------------------
------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and
stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to