Have you tried Condition?
-Original Message-
From: Majcica, Mario [mailto:mario.majc...@bakerhughes.com]
Sent: Tuesday, December 09, 2014 4:14 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] Setting properties value
Hi,
I declared a property in the following way
(why do people always jump to assuming it's a bug first? )
Your Property and IniFileSearch are in a Fragment that is never referenced.
You need to reference the content in there. Give the example, I would add a
PropertyRef under the Product element somewhere to the Property for the
IniFileSearch.
> > >
> > > Edwin G. Castro
> > > Software Developer - Staff
> > > Electronic Banking Services
> > > Fiserv
> > > Office: 503-746-0643
> > > Fax: 503-617-0291
> > > www.fiserv.com
> > > Please consider the environment before prin
www.fiserv.com
> > Please consider the environment before printing this e-mail
> >
> >
> > > -Original Message-
> > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
> > > Sent: Thursday, January 27, 2011 1:46 PM
> > > To: General
erv.com
> Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
> > Sent: Thursday, January 27, 2011 1:46 PM
> > To: General discussion for Windows Installer XML toolset.
olbreeze...@googlemail.com]
> Sent: Thursday, January 27, 2011 1:46 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Setting properties
>
> Edwin,
>
> I have the Wix book and it showed ExecuteAction as the last action in
> InstallU
;
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: Cool
gt; > Fiserv
> > Office: 503-746-0643
> > Fax: 503-617-0291
> > www.fiserv.com
> > P Please consider the environment before printing this e-mail
> >
> >
> > > -Original Message-
> > > From: CoolBreeze [mailto:coolbreeze...@googlemai
x: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
> > -Original Message-
> > From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
> > Sent: Wednesday, January 26, 2011 3:30 PM
> > To: wix-users@lists.sourc
age-
> From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
> Sent: Wednesday, January 26, 2011 3:30 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Setting properties
>
> Hi Guys, I'm still trying to get this resolved. When I viewed the log fil
Hi Guys, I'm still trying to get this resolved. When I viewed the log file I
could see that my property contained the value I assigned to it from within
my CustomAction; however, it doesn't contain anything when I try use it
within the wrote:
> I have a property I've set within a CustomAction that
Any ideas as to why I'm not able to get the value from the property when it
appears to be getting set as per the log?
--Lance
On Tue, Jan 25, 2011 at 1:40 PM, CoolBreeze wrote:
> I'm calling it within InstallUISequence and after ExecuteAction.
>
>
>
>
>
> It looks like it is being set prop
I'm calling it within InstallUISequence and after ExecuteAction.
It looks like it is being set properly, if I'm interpreting the log
correctly.
Action ended 13:19:57: CostFinalize. Return value 1.
Action 13:20:08: CheckDbConnectionDlg. Dialog created
MSI (c) (FC:34) [13:20:13:371]: PROPERT
In which sequence and where in that sequence are you calling your custom
action, and is that property marked "Secure"?
BTW, a verbose log can tell you exactly what is (and isn't) happening with
that property.
-Blair
-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com
This seems to have worked - thanks very much.
David
> -Original Message-
> From: Blair [mailto:os...@live.com]
> Sent: 22 December 2009 13:45
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Setting properties in custom
Windows Installer evaluates component conditions during CostFinalize, so
your custom action that sets those session values must be scheduled before
then. I would recommend scheduling those types of actions to run before
CostInitialize, just to have a "smoother" flow.
-Original Message-
Fro
The on the components is evaluated during CostFinalize, not
CreateShortcuts. You don't get the shortcuts because the components
installing the shortcuts are not being installed due to the false condition
on them.
I would recommend moving your CheckApplicationLicence custom action sequence
to befo
See
http://msiext.codeplex.com/sourcecontrol/changeset/view/47269?projectName=msiext#816368.
Look at MsiInstall::GetFormattedString.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: mrtn [mailto:mrtn.frederik...@gmail.com]
Sent: Monday, October 19, 2009 10:1
There is no C++ expand that will resolve msi properties. You could "get" the
property from msi or "set" the property. That is what you set the property
to.
-Original Message-
From: mrtn [mailto:mrtn.frederik...@gmail.com]
Sent: Monday, October 19, 2009 10:12 AM
To: wix-users@lists.sourcef
MsiFormatRecord()
Call MsiSetProperty with the resulting buffer.
-Original Message-
From: mrtn [mailto:mrtn.frederik...@gmail.com]
Sent: Monday, October 19, 2009 7:12 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Setting properties in a C++-CA vs. setting properties
using
"Brian Simoneau" <[EMAIL PROTECTED]> writes:
> What you have is not terribly messy, at least when it comes to Windows
> Installer.
Well than please let me know how to do it. The below code does not
work properly, I can not see any reason why this boolean stuff should
not work, but either the fil
-users] Setting properties
"Brian Simoneau" <[EMAIL PROTECTED]> writes:
> Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
> PROP1 exists. Something like
> Value="[PROP1]"/>
> PROP1
> You can do the same thing for PROP2 or set PROP2
"Brian Simoneau" <[EMAIL PROTECTED]> writes:
> Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
> PROP1 exists. Something like
> Value="[PROP1]"/>
> PROP1
> You can do the same thing for PROP2 or set PROP2 as the default value of
> ANOTHER_PROP since it is the else case.
W
Oops, nevermind. The condition goes inside the Custom element in the
install sequence, not in the CustomAction element.
Tim
On Thu, Jun 12, 2008 at 11:50 AM, Tim Fisher <[EMAIL PROTECTED]> wrote:
> If I try to compile that, it tells me the CustomAction element
> contains illegal inner text. :(
>
If I try to compile that, it tells me the CustomAction element
contains illegal inner text. :(
Tim
On Thu, Jun 12, 2008 at 11:08 AM, Brian Simoneau
<[EMAIL PROTECTED]> wrote:
>
> Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
> PROP1 exists. Something like
> Value="[PROP
Use a custom action to set ANOTHER_PROP to PROP1 with a condition that
PROP1 exists. Something like
PROP1
You can do the same thing for PROP2 or set PROP2 as the default value of
ANOTHER_PROP since it is the else case.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[
26 matches
Mail list logo
