I think your problem is due to using Level="0". See ->
http://msdn.microsoft.com/en-us/library/aa369536.aspxPersonally I would recommend you don't set your property to anything to
start with, simply use RegistrySearch to set it (so it will be null
unless your RegistrySearch is successful) & change your condition to:
<Condition Level="1"><![CDATA[FOUND_VC80DIR OR Installed]]></Condition>
as well as changing the Feature's Level to 9999 (or higher if you use
INSTALLLEVEL's as high as 9999 & above but 9999 should be high enough
for most people).
This should make it only install if the FOUND_VC80DIR has a value set &
should make it always uninstall.
Works for me in 3 (or 12 depending on whether you count the supported
applications individually rather than the features it's implemented in)
almost identical situations to this.
Good Luck.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the <Virtual Environment>**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-----Original Message-----
From: Rob Hamflett [mailto:
[hidden email]]
Sent: 27 October 2009 15:26
To:
[hidden email]
Subject: [WiX-users] Feature not properly uninstalled when Level 0
I've got a feature that I only want to be installed if Visual Studio
2005 C++ is installed. I search the registry for a particular value to
indicate if it is present or not, and set this value to a property
called FOUND_VC80DIR, which initially has the value of "UNKNOWN". On my
feature I have this condition:
<Condition Level="0"><![CDATA[FOUND_VC80DIR = "UNKNOWN"]]></Condition>
I'm trying to work out how to get my product to uninstall after the user
has removed Visual Studio.
I install my product, remove the VS value I reference (to simulate an
uninstall without actually having to sit through it) and then uninstall
my product. The product is uninstalled but it leaves behind the files
from this feature. I tried adding "AND NOT REMOVE" to the condition,
but this only seems to work if if I uninstall it by using the "msiexec
/x" from the command line. If I go through the UI and choose to remove
it then I am still left with the files. Can anyone let me know how to
get round this?
Thanks,
Rob
------------------------------------------------------------------------
------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
