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
I am using these conditions but they are behaving strangly:
NOT
InstalledNOT Installed
(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR
NOT(REMOVE = "ALL")(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR
NOT(REMOVE = "ALL") OR (Installed AND (InstallMode =
"Repair"))
Installed AND (InstallMode = "Repair
conditions ( Condition element nested under a
> Component element ) and the VersionNT property.
>
>
>
> From: "Anil Patel"
>
> Sent: Monday, September 05, 2011 9:29 AM
>
> To: "General discussion for Windows In
05, 2011 9:29 AM
To: "General discussion for Windows Installer XML toolset."
Subject: [WiX-users] Conditions on a Fragment
Hello,
I have a number of fragments say A, B & C.
What I would like to do is to install fragment A if the the OS is Windows
7,
install fragment B if the
Hello,
I have a number of fragments say A, B & C.
What I would like to do is to install fragment A if the the OS is Windows 7,
install fragment B if the OS is Win XP and install fragent C if its Windows
Vista.
So its a selective install of fragments based on OS.
I thought of using a condition el
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:
Hi
I'm trying to uninstall an old app that was made with suxxx NSIS installer
and need to upgrade it to MSI. What could be the best way? I tried to make a
registry search and set the UNINSTALLNSIS property.
I ran MSI with debug mode and see the property has been set:
MSI (c) (78:40) [15:40:42:577
M
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Conditions on - how do Imake it dependent on a
Hi,
I am attempting to customise my installer dialogs.
I have a that prompts for a database instance
name - but I only want to display the Dialog if the user has opte
Hi,
I am attempting to customise my installer dialogs.
I have a that prompts for a database instance
name - but I only want to display the Dialog if the user has opted to
install
On the previous I have this:
[CDATA[(&DbFeature=3)]]
This is giving an error:
Entity 'DbFeature' not defined.
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] Condition
How can I create conditions for a custom action to run for Uninstall/Remove
only?
If I use condition 'Installed' then the CA runs in Repair mode.
If I use condition 'Remove="ALL"' then the CA doesn't run in Repair, but it
doesn't run in Uninstall/Remove either.
Thanks.
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/
[mailto:shabbir_ah...@hotmail.com]
Sent: Tuesday, March 09, 2010 11:03 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] conditions
Hi,
I am tyring to use a condition to check if a pre-requisite application
is installed. The way I am doing it is to set a property with a
registry
Hi,
I am tyring to use a condition to check if a pre-requisite application is
installed. The way I am doing it is to set a property with a registry search.
I am checking this preperty in a condition, nd want the installation to stop if
the registry is not found, and display a message to t
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
Hi All,
I've got a problem with my condition using a property.
I set this property in the UI with my own dialog buttons which have the
following code.
1
1
On the fragment of the feature I set the property to a default:
On my feature I have the following condition:
In the logfile
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
riginal Message-
From: Ken Halprin [mailto:khalp...@autosoln.com]
Sent: Wednesday, December 09, 2009 10:08 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditions in merge modules
I'm creating a merge module for inclusion in another company's msi package.
It does not app
I'm creating a merge module for inclusion in another company's msi package.
It does not appear to be possible to put conditions (such as checking
operating system version or .net installed version) in the merge module.
How is that generally handled?
Thanks.
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
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 tested variable it appears like it should be
Sample
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
When using XMLConfig from UtilExtension, a SchedXmlConfig entry is created in
the InstallExecuteSequence table with condition set to VersionNT > 400.
Is there any way of specifying additional conditions? I would need a way to
allow users to select if they want to remove the config or not since i
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/
-
I see there is a RegistrySearch, FileSearch, DirectorySearch, AppSearch ..
and even an IniFileSearch. Is there such a thing as XMLFileSearch?
I'd like to do some conditional processing based on XML. Any solutions out
there?
- Troy
20, 2009 4:49 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Conditions in fragments
>
> I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment
> with only launch conditions, I've realized that even with compile
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
XML toolset.
Subject: [WiX-users] Conditions in fragments
I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment
with only launch conditions, I've realized that even with compile propriety
in the solution that fragment was ignored, unless I had a propriety or a
custom
I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment
with only launch conditions, I've realized that even with compile propriety in
the solution that fragment was ignored, unless I had a propriety or a custom
action in that fragment linked or sub linked to the , just a war
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
I'm try to check the file version of a required library as part of
condition. I have code that looks like:
AProduct
AProduct >= 1.6
My first condition works ok (ie: the installation fails if the required
product is not installed) but my second condition (which checks the
version) d
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
;
>
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett
> Sent: Dienstag, 26. Juni 2007 17:17
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] [wix-users] Conditions for setup in
Oliver Friedrich
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett
Sent: Dienstag, 26. Juni 2007 17:17
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] [wix-users] Conditions for setup in GUI and without
GUI?
Yuo could create cus
Another info from MSDN (Windows Installer Error Messages):
Windows Installer errors have an error code of 1000 or greater. The
error codes numbered 1000 to 1999 are ship errors and must be
authored into the Error table. The error codes numbered greater than
2000 are internal errors and do not have
Hmm, haven't seen that before. I've been using 2000+ for all my error codes.
Should probably get
round to fixing that some day, then.
Rob
Stefan Pavlik wrote:
> I know that the code below is just an example but to be precise:
>
> MSDN: Error Table
> The range from 25000 to 3 is reserved
I know that the code below is just an example but to be precise:
MSDN: Error Table
The range from 25000 to 3 is reserved for errors from custom
actions. Authors of custom actions may use this range for their
custom actions.
Regards
Stefan
Rob Hamflett wrote:
> Yuo could create custom erro
Yuo could create custom errors like this:
This is my error message
and create a custom action to trigger it like this:
You can call this in the InstallExecuteSequence like this:
NOT WANTED_CONDITION
The additional problem is how do you stop them triggering if the UI ran?
You can create another
Hi WiX-Users,
in our Setup we use a personalized GUI, that checks in its first dialog several
conditions and shows messages, if one condition fails. Most of this conditions
handle previously needed software, like "MMC 3.0" and "Powershell 1.0".
This just works fine for us, but if the install is
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
I have features that I need changed based on user input. However they are
based on information gained through my External UI sequence. Is there a way
in code to call something that would produce the same results as
--
View this message in context:
http://www.nabble.com/Conditions-on-Feature-
users@lists.sourceforge.net
Subject: [WiX-users] Conditions for Custom Actions
Is there a way to conditionally run a custom action based on a
property value?
So I want to run the custom action only if PROP1’s value
remains unchanged.
Thanks
Sar
Is there a way to conditionally run a custom action based on a property value?
So I want to run the custom action only if PROP1’s value remains unchanged.
Thanks
Saranath
-
Take Surveys. Earn Cash. Influence
gt; Sent: Monday, September 18, 2006 10:31 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Conditions and version of OS
>
>
> Salut,
>
> trying to create my first setup using WIX. My software does not support
> Windows 95. In the http://www.tramontana.co.h
AIL PROTECTED]
Sent: Monday, September 18, 2006 10:31 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditions and version of OS
Salut,
trying to create my first setup using WIX. My software does not support
Windows 95. In the http://www.tramontana.co.hu/wix/lesson1.php#1.4 wix
t
Salut,
trying to create my first setup using WIX. My software does not support
Windows 95. In the http://www.tramontana.co.hu/wix/lesson1.php#1.4 wix
tutorial I found the following lines:
Version9X =
400
Version9X = 400 AND
WindowsBuild =
Unfortunately I get the message "Operatin
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
60 matches
Mail list logo
