On 22-Sep-10 13:07, Matt Walker wrote:
> I don't know if I mentioned this before, but my Deferred Custom Action
> fires an .exe stored in the Binary Table with the following command line
> parameters being passed [ProductCode] [OURVERSION], the later being the
> pre-populated property.
The reaso
do not necessarily represent those of the
company.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Wednesday, September 22, 2010 12:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters toDeferred Cus
d.
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Tuesday, September 21, 2010 5:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred
CustomAction on Vista
Briefly, CustomActionData i
s.com]
Sent: Tuesday, September 21, 2010 5:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred
CustomAction on Vista
Briefly, CustomActionData is a parameter passing scheme to get property
values passed to a deferred custom a
sequence.
Phil Wilson
-Original Message-
From: Superfreak3 [mailto:matt.wal...@synergis.com]
Sent: Tuesday, September 21, 2010 11:59 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Command Line Parameters to Deferred Custom Action on
Vista
So what exactly is the
So what exactly is the difference between SecureCustomProperties and
CustomActionData? I still do not fully understand this.
We have a public property that holds a string that we write to the registry
in certain cases. Is is held in the Property table. Let's say it contains
8.1.2.3 and is call
...@gmail.com]
Sent: Friday, April 17, 2009 12:15 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista
Hi,
I am developing a WiX installer for Vista. I have a requirement to send some
command line parameters to a Deferred Cusom action
Rajesh P wrote:
> I am developing a WiX installer for Vista. I have a requirement to send some
> command line parameters to a Deferred Cusom action.
>
Then you must use CustomActionData; deferred custom actions can't
otherwise get property values.
--
sig://boB
http://joyofsetup.com/
-
h P [mailto:rajeshp.bl...@gmail.com]
Sent: Friday, April 17, 2009 12:15 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista
Hi,
I am developing a WiX installer for Vista. I have a requirement to send some
command line parameters to a Deferred Cu
Hi,
I am developing a WiX installer for Vista. I have a requirement to send some
command line parameters to a Deferred Cusom action.
My inital attempts to send the parameters using public property as follows
have failed:
I tried : msiexec /i myinstaller.msi CMDLINEPROPERTY="arg1 arg2 arg3"
But t
Ah so simple
--
View this message in context:
http://www.nabble.com/Command-line-parameters-tf4666532.html#a13332073
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.net email is sponsored by: Splunk I
In article <[EMAIL PROTECTED]>,
RussGreen <[EMAIL PROTECTED]> writes:
> What I want to be able to do is pass in a value for this property from the
> command line but that only works when RegistrySearch is commented out.
As Peter Marcu suggested, use a different property for the value
retrie
RussGreen
Sent: Sunday, October 21, 2007 8:56 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Command line parameters
I have 2 public properties in my MSI file. Each property is set a default
value as well has a registrysearch to find a value..
e.g.
What I want to be able
I have 2 public properties in my MSI file. Each property is set a default
value as well has a registrysearch to find a value..
e.g.
What I want to be able to do is pass in a value for this property from the
command line but that only works when RegistrySearch is commented out.
14 matches
Mail list logo
