I am using these conditions but they are behaving strangly:
InstallExecuteSequence!--Set properties for Installation--Custom
Action=CA_SetProperty_MACHINENAME After=CostFinalizeNOT
Installed/CustomCustom Action=CA_SetProperty_SDK_MACHINE
After=CA_SetProperty_MACHINENAMENOT Installed/Custom
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 raviraj.callin...@gmail.comwrote:
I am using these conditions but they are behaving strangly:
InstallExecuteSequence!--Set properties for Installation--Custom
ok i got this Remove=ALL works great.
On Thu, Jun 14, 2012 at 2:19 PM, Ravi Raj raviraj.callin...@gmail.comwrote:
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 raviraj.callin...@gmail.comwrote:
I am using
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
, September 05, 2011 9:29 AM
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
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
: [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 OS is Win XP and install fragent C if its
Windows
Vista.
So its a selective install
On 30-Jul-11 10:07, Marc Bauer wrote:
Condition Message=Previous version of MyApp installed.UNINSTALLNSIS AND
NOT Installed/Condition
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
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)
Hi,
I am attempting to customise my installer dialogs.
I have a Dialog Id=SqlSpecDlg that prompts for a database instance
name - but I only want to display the Dialog if the user has opted to
install Feature Id=DbFeature
On the previous Dialog I have this:
Publish Dialog=CustomizeDlg
-Original Message-
From: Jamie Thomson
Sent: Friday, February 11, 2011 5:15 PM
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 Dialog Id=SqlSpecDlg
.
From: Sanjay Raos...@noida.interrasystems.com
To: General discussion for Windows Installer XML
toolset.wix-users@lists.sourceforge.net
Sent: Wed, March 31, 2010 11:02:18 PM
Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only
try out this one
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
: Re: [WiX-users] Conditions for Uninstall/Remove Only
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
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.
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
Subject: [WiX-users] Conditions for Uninstall/Remove Only
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
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
[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 Igor,
thanks. Moving the condition out of component and just under package sorted
it!!
_
Got a cool Hotmail story? Tell us now
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
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.
!--The DEPLOYMENTTYPE buttons--
Control Id=AllInOne Type=PushButton Height=41 Width=41 X=72
Y=80 Bitmap=yes Text=AllInOneImg
Publish
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.
-
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 appear to be possible to put
.'
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 components and/or custom
actions your
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 which
produces
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
Property Id='OSINSTALLDIR'
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 tested
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:
InstallExecuteSequence
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 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
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/
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 action
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
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 propriety
in the solution that fragment was ignored
I'm try to check the file version of a required library as part of
condition. I have code that looks like:
Property Id=AProduct
RegistrySearch
Id='AProduct.Registry'
Type='raw'
Root='HKLM'
Key='SOFTWARE\SomeCompany\SomeProduct'
Name='CurrentVersion'
/
/Property
Craig Ward wrote:
Condition Message=This program requires version 1.6 or above of
SomeProduct
AProduct = 1.6
/Condition
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
] [wix-users] Conditions for setup in GUI and without
GUI?
Yuo could create custom errors like this:
Error Id=2000This is my error message/Error
and create a custom action to trigger it like this:
CustomAction Id=MyError Error=2000 /
You can call this in the InstallExecuteSequence like
]
[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 custom errors like this:
Error Id=2000This is my error message
of the
condition. Maybe it is a bug?
Oliver Friedrich
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
Hi Wix-users,
Solved the problem, easier than thought. To disable LaunchConditions in UI Mode
simply add the following:
InstallUISequence
LaunchConditions Suppress='yes'/
/InstallUISequence
Important, must be in InstallUISequence so that the LaunchConditions are run
if the msi is
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
@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 property, right?
Rob
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
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 for
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
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 Publish
Event=AddLocalValue=FeatureId/
--
View this message in context:
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
Is there a way to conditionally run a custom action based on a property value?
Property Id=PROP1 value=None /
Custom action="">
So I want to run the custom action only if PROP1s value remains unchanged.
Thanks
Saranath
Subject: [WiX-users] Conditions for Custom Actions
Is there a way to conditionally run a custom action based on a
property value?
Property Id=PROP1 value=None /
Custom
action="">
So I want to run the custom action only if PROP1s value
rema
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:
Condition Message='Operating system not supported!'Version9X =
400/Condition
Condition
: 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
tutorial I found
: 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
tutorial I found
To: Scott Sam;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users]
conditions
What are you trying to do overall?
Using feature conditions in a components condition is a little awkward
usually features directly determine if a component will be installed.
Derek
From:
[EMAIL PROTECTED
I have a component that looks like:
Component Id=DbInstallationDirectoryService
Guid=A4B5E633-D715-4e8e-8C4A-E58D1BAFFBAE
XmlFile Action="" ElementPath=//DBInstallation/FeaturesInstalled
File=[DBCREATION]dbinstallation.xml
Id=dbInstallationConfig20 Name=Feature
Sequence=19 Value=Feat1 /
, July 26, 2006
12:25 PM
To:
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
conditions
I have a component that looks like:
Component Id=DbInstallationDirectoryService
Guid=A4B5E633-D715-4e8e-8C4A-E58D1BAFFBAE
XmlFile Action="" ElementPath=//DBInstallation/FeaturesInst
;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users]
conditions
What are you trying to do overall?
Using feature conditions in a components condition is a little awkward
usually features directly determine if a component will be installed.
Derek
From:
[EMAIL PROTECTED] [mailto
56 matches
Mail list logo
