ok i got this Remove="ALL" works great.
On Thu, Jun 14, 2012 at 2:19 PM, Ravi Raj wrote:
> I have checked that InstallMode = "Repair" or InstallMode = "Remove" is
> not working at all.
>
>
> On Thu, Jun 14, 2012 at 12:56 PM, Ravi Raj wrote:
>
>> I am using these conditions but they are behaving s
I have checked that InstallMode = "Repair" or InstallMode = "Remove" is not
working at all.
On Thu, Jun 14, 2012 at 12:56 PM, Ravi Raj wrote:
> I am using these conditions but they are behaving strangly:
>
> Action="CA_SetProperty_MACHINENAME" After="CostFinalize">NOT
> Installed After="CA_SetP
Thanks Christopher.
I'll look at component conditions.
Regards,
Anil.
On Mon, Sep 5, 2011 at 3:46 PM, Christopher Painter <
chr...@deploymentengineering.com> wrote:
>
>
> Fragments are a compiler/build concept not an installer/runtime concept.
> Take a look at component conditions ( Condition
Fragments are a compiler/build concept not an installer/runtime concept.
Take a look at component conditions ( Condition element nested under a
Component element ) and the VersionNT property.
From: "Anil Patel"
Sent: Monday, September 05, 2011 9:29
On 30-Jul-11 10:07, Marc Bauer wrote:
> UNINSTALLNSIS AND
> NOT Installed
Launch conditions indicate the condition that are required for install
to proceed; if the condition isn't met, the install is canceled with the
specified message. Your condition is being met, so there's no error.
--
sig:
Sorry, please ignore. I was making this much more difficult than it had to
be. This seems to be what I want:
&DbFeature=3
Hopefully will help someone who might one day search for this anyway!!!
JamieT
-Original Message-
From: Jamie Thomson
Sent: Friday, February 11, 2011 5:15 PM
To: G
le - much clearer.
>
>
>
>
> From: Sanjay Rao
> To: General discussion for Windows Installer XML
> toolset.
> Sent: Wed, March 31, 2010 11:02:18 PM
> Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only
>
> try out this one.
> (NOT
Thanks Sanjay.
This is great. Especially there is a table - much clearer.
From: Sanjay Rao
To: General discussion for Windows Installer XML toolset.
Sent: Wed, March 31, 2010 11:02:18 PM
Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only
try out
try out this one.
(NOT UPGRADINGPRODUCTCODE) AND (REMOVE="ALL")
for more details u can see
http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi
-Sanjay
little.forest wrote:
> How can I create conditions for a custom action to run for Un
Thanks Phil!
That works. Sorry, I didn't pay attention on that.
From: "Wilson, Phil"
To: General discussion for Windows Installer XML toolset.
Sent: Wed, March 31, 2010 4:17:59 PM
Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only
That's because property names are case sensitive and the actual name is REMOVE.
Phil Wilson
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Wednesday, March 31, 2010 3:55 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditions for Uninstal
Hi Igor,
thanks. Moving the condition out of component and just under package sorted
it!!
_
Got a cool Hotmail story? Tell us now
http://clk.atdmt.com/UKM/go/195013117/direct/01/
Hi,
You are trying to create Launch Condition and refer to Wix documentation
to create Launch Condition you Condition element should be child node
under Product or Fragment element, so you simply need to remove
Component above your Condition.
Igor
-Original Message-
From: Shabbir Ahsan [
Jeffrey Bindinga wrote:
> In the logfile I see that the property is set on the UI and the INSTALL (no
> typo's either), but my condition still evaluates to false while
> DEPLOYMENTTYPE is AllInOne.
>
See http://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/.
--
sig://boB
http://joyo
ginal Message-
From: Ken Halprin [mailto:khalp...@autosoln.com]
Sent: Wednesday, December 09, 2009 11:58 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Conditions in merge modules
To get a feel for how wix works, I created an installer project wh
ML toolset.'
Subject: Re: [WiX-users] Conditions in merge modules
Are you talking about LaunchConditions, Feature conditions, or Component
conditions?
You can't "isolate" your merge module parts in a final MSI very easily, but
you should be able to condition any/all of your co
Are you talking about LaunchConditions, Feature conditions, or Component
conditions?
You can't "isolate" your merge module parts in a final MSI very easily, but
you should be able to condition any/all of your components and/or custom
actions your merge module contributes.
-Original Message---
Does a verbose log file show the Property getting set?
Patrick Sullivan wrote:
> Moderate time user, first time question asker.
>
>
>
> I'm having issues where my protection condition around a component that
> includes an inifile is not working correctly, yet when I include the value
> of the test
Again, I found my solution by myself:
To define custom conditions for the SchedXmlConfig action that gets added when
you use XMLConfig, you simply have to reschedule it in the
installExecuteSequence and there, you will be able to set your own conditions.
For instance:
VersionNT > 400
AND
troy hostetter wrote:
> I see there is a RegistrySearch, FileSearch, DirectorySearch, AppSearch ..
> and even an IniFileSearch. Is there such a thing as XMLFileSearch?
>
Not in WiX today.
--
sig://boB
http://joyofsetup.com/
-
Ick.
Eitan Behar wrote:
> You can also have an empty component group and add reference to it from the
> product file. - this is what I do :^)
>
>
> -Original Message-
> From: Frederico Rico Apostolo [mailto:frederico.apost...@vantyx.com]
> Sent: Friday, February 20, 2009 4:49 PM
> To: Ge
You're right. Conditions are one thing that don't have a good way to
reference. Maybe put the Properties referenced by the Conditions in the
same Fragment, then use a PropertyRef?
Frederico Rico Apostolo wrote:
> I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment
> wi
You can also have an empty component group and add reference to it from the
product file. - this is what I do :^)
-Original Message-
From: Frederico Rico Apostolo [mailto:frederico.apost...@vantyx.com]
Sent: Friday, February 20, 2009 4:49 PM
To: General discussion for Windows Installer X
Craig Ward wrote:
>
> AProduct >= 1.6
>
>
The MSI doc says "floating point numeric values are not supported." The
general approach MSI offers for version comparisons is via AppSearch. In
WiX, you could use RegistrySearch to get the path and FileSearch to
confirm its version.
--
sig://b
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Conditions for setup in GUI and without GUI?
Just a sanity check. In your last message you said you were setting a UI_RAN
property, but in your
examples you're checking against a GUI property. You are setting and using the
same proper
gt; Consultant - Software Solutions
>
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett
> Sent: Mittwoch, 27. Juni 2007 12:59
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Conditions f
Hi Wix-users,
Solved the problem, easier than thought. To disable LaunchConditions in UI Mode
simply add the following:
Important, must be in so that the LaunchConditions are run
if the msi is executed quiet.
Thx for all hints.
Oliver Friedrich
-
h
Consultant - Software Solutions
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett
Sent: Mittwoch, 27. Juni 2007 12:59
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Conditions for setup in GUI and without GUI?
You've set suppres
You've set suppress="yes", which means the event doesn't occur.
Rob
Mailinglist wrote:
> Hi,
>
>
>
> Thank you for your hints, but this just doesn't work correctly.
>
>
>
> I do not need to create custom errors, if statements do the
> same. So the helpful thoughts are in the lower part
Hi,
Thank you for your hints, but this just doesn't work correctly.
I do not need to create custom errors, if statements do the same.
So the helpful thoughts are in the lower part of your mail.
That however does not work. If I set the UI_RAN property, the condition only
fails if the NOT_W
MsiSetFeatureState?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Magus
Sent: Monday, March 05, 2007 5:32 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditions on Feature
I have features that I need changed based on user input. Howeve
Yes. You don't need the square brackets around the Property.
I suggest reading the MSI SDK topic about Condition Syntax.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Saranath Aravamudhan
Sent: Saturday, September 23, 2006 00:50
To: wix-users@lists.sourceforge.net
Salut,
thanks. I changed it to
Version9X =
400
and it gives me no error anymore. Next time I get the chance to test it on
Windows 95 I'll see if it works completely correct ;)
Stefan
Matthew Janulewicz-2 wrote:
>
> In Wix, and with MSI installers in general I believe, the condition has
In Wix, and with MSI installers in general I believe, the condition has
to be *true* to install. So in these cases, you will *only* be able to
install on Windows 95. I believe you want to change your '=' to 'NOT'.
-Matt
-Original Message-
From: vbtricks [mailto:[EMAIL PROTECTED]
Sent:
I have a component that looks like:
From my understanding, it should right out
Feat1 if the Feature1 feature is being
installed, and it is not an upgrade. That is not what is happening.
What am I doing wrong? What is the
: Scott Sam;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users]
conditions
What are you trying to do overall?
Using feature conditions in a component’s condition is a little awkward
– usually features directly determine if a component will be installed.
Derek
From
;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users]
conditions
What are you trying to do overall?
Using feature conditions in a component’s condition is a little awkward
– usually features directly determine if a component will be installed.
Derek
From:
[EMAIL PROTECTED
, July 26, 2006
12:25 PM
To:
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
conditions
I have a component that looks like:
From my understanding, it should right out
Feat1 if the Feature1 feature is being
installed
I have a component that looks like:
From my understanding, it should right out
Feat1 if the Feature1 feature is being
installed, and it is not an upgrade. That is not what is happening.
What am I doing wrong? What is the
39 matches
Mail list logo
