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
