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

2010-09-22 Thread Bob Arnson
  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 reason it works is that your deferred action is being scheduled 
during the script generation phase of the execute sequence, when 
properties are still available. Your CA isn't trying to read properties 
-- it's an .exe whose command line was set when it was scheduled. 
SecureCustomProperties is necessary to get a property out of the UI 
sequence and into the script generation phase of the execute sequence. 
SecureCustomProperties won't get a property into the *script execution* 
phase of the execute sequence; that's what CustomActionData is for.

-- 
sig://boB
http://joyofsetup.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


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

2010-09-22 Thread Matt Walker
I guess I'm still a little foggy on it so I'll keep digging.  If
CustomActionData is needed to get values to Deferred Custom Actions, how
then is my property value, populated in the Property Table, getting to
my deferred action?  In addition to having the property pre-populated in
the table, I also added it to SecureCustomProperties.  However I'm not
using the Set Directory CA mechanism to get the value to
CustomActionData.

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.

I don't know why, but I can't seem to get a handle on this!  :(


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and 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 CustomAction
on Vista

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 P