Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista

2010-09-22 Thread Wilson, Phil
They are still two separate items. SecureCustomProperties is need if you want 
to pass properties from the UI to the execute sequence, whether they get passed 
to custom actions or not. If you pass them to a immediate custom actions 
there's no need to use CustomActionData. So if you wanted to collect a property 
value in the UI sequence AND pass it to a deferred custom action then you'd 
need to use SCP to get it into the execute sequence AND use CustomActionData to 
pass it to a deferred custom action. 

You might be thinking that CustomActionData is a single property, but it's not. 
Every deferred custom action can have its own CustomActionData associated with 
it. Yes, it's used to pass property values into deferred custom actions. You 
simply cannot directly get property values in deferred custom actions, that's 
what CustomActionData is for. 

There'a a paragraph or two at the end here 
http://msdn.microsoft.com/en-us/library/aa370543(VS.85).aspx 

Phil Wilson 


-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Tuesday, September 21, 2010 6:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred CustomAction on 
Vista

Since both worked in my scenario, I still, really don't know the
difference.

When you say SCPs is used to pass property values to the execute
sequence, does that include access during or for deferred custom
actions?  Or, is CAD used to pass information to the deferred actions?

Would there be a good example to illustrate the need for the use of
CustomActionData where simply adding a property to
SecureCustomProperties would not provide access during the deferred
sequence?

Any further help greatly appreciated.

-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 is a parameter passing scheme to get property
values passed to a deferred custom action. SecureCustomProperties is a
list of properties that you want to pass from the UI sequence (where you
probably collected their values) across the context boundary into the
execute 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 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 called OURVERSION.

I have a little widget that runs near the end of the install that tests
the
condition for the registry edit and edits accordingly.  I used a Set
Property custom action sequenced in the Immediate Sequence to set the
above
mentioned property to something like PASSDATAACTION.  

Then, in the Deferrec Sequence action, I reference CustomActionData that
now
holds the value I passed.  All seems to work OK here.

I then thought, lets add the original property, OURVERSION, to
SecureCustomProperties and just reference that directly as a parameter
in my
Deferred action, guess what.  This works too.

So, I'm unclear as to the true purpose of each.

I know this really is off WiX topic, but I've gotten great help here
before
so any now is greatly appreciated.  The scenario described above may not
be
exactly what is going on, but just to give an example.

Thanks in advance for any help!!
-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Command-Li
ne-Parameters-to-Deferred-Custom-Action-on-Vista-tp2652448p733.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which
it is addressed. This e-mail is confidential and may well also be
legally privileged. If you have received it in error, you are on notice
of its status. Please notify the sender immediately by reply e-mail and
then delete this message from your system. Please do not copy it or use
it for any purposes, or disclose its contents to any other person. This
email comes from a division

Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista

2010-09-21 Thread Matt Walker
Since both worked in my scenario, I still, really don't know the
difference.

When you say SCPs is used to pass property values to the execute
sequence, does that include access during or for deferred custom
actions?  Or, is CAD used to pass information to the deferred actions?

Would there be a good example to illustrate the need for the use of
CustomActionData where simply adding a property to
SecureCustomProperties would not provide access during the deferred
sequence?

Any further help greatly appreciated.

-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 is a parameter passing scheme to get property
values passed to a deferred custom action. SecureCustomProperties is a
list of properties that you want to pass from the UI sequence (where you
probably collected their values) across the context boundary into the
execute 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 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 called OURVERSION.

I have a little widget that runs near the end of the install that tests
the
condition for the registry edit and edits accordingly.  I used a Set
Property custom action sequenced in the Immediate Sequence to set the
above
mentioned property to something like PASSDATAACTION.  

Then, in the Deferrec Sequence action, I reference CustomActionData that
now
holds the value I passed.  All seems to work OK here.

I then thought, lets add the original property, OURVERSION, to
SecureCustomProperties and just reference that directly as a parameter
in my
Deferred action, guess what.  This works too.

So, I'm unclear as to the true purpose of each.

I know this really is off WiX topic, but I've gotten great help here
before
so any now is greatly appreciated.  The scenario described above may not
be
exactly what is going on, but just to give an example.

Thanks in advance for any help!!
-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Command-Li
ne-Parameters-to-Deferred-Custom-Action-on-Vista-tp2652448p733.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which
it is addressed. This e-mail is confidential and may well also be
legally privileged. If you have received it in error, you are on notice
of its status. Please notify the sender immediately by reply e-mail and
then delete this message from your system. Please do not copy it or use
it for any purposes, or disclose its contents to any other person. This
email comes from a division of the Invensys Group, owned by Invensys
plc, which is a company registered in England and Wales with its
registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW
(Registered number 166023). For a list of European legal entities within
the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_i
d=77.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
recept...@invensys.com. This e-mail and any attachments thereto may be
subject to the terms of any agreements between Invensys (and/or its
subsidiaries and affiliates) and the recipient (and/or its subsidiaries
and affiliates).




--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Start uncovering the many advantages of virtual appliances
and start using them