Secure is not required to pass from the UI to the Execute sequence, it's required to pass to the *server side* in the Execute sequence. (i.e. deferred CAs)
Take a look at the diagram on http://blogs.msdn.com/rflaming/archive/2006/09/21/765452.aspx - Pink is UI, Yellow is Execute and Green is basically server side/deferred actions (stuff that should be rolled back when install fails) The way I see it (I might be wrong here) Non-secured properties can move between Pink/Yellow, but only secure properties can move between Yellow/Green or Pink/Yellow/Green. Someone else more familiar with MSI internals and terminology might be able to give a better explanation :) Sascha On Fri, Apr 30, 2010 at 8:00 AM, Matt Johnson <ma...@timeamerica.com> wrote: > Lol. See my prior posts from today. I needed this specifically to get a > property from a registry key to pass to a custom action during uninstall. > > > Matt Johnson MCPD, MCTS, MCSD, MCDBA > Director of Application Development > Time America, Inc. > ma...@timeamerica.com | www.timeamerica.com > > > -----Original Message----- > From: Nick Ramirez [mailto:nickra...@hotmail.com] > Sent: Thursday, April 29, 2010 2:48 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Property/@Secure - when to use? > > > Hello, > > The Property element's Secure attribute is supposed to be necessary to pass > a property from the UI to the Execute sequence. However, I've never been > able to create a situation where it was necessary. For me, just making the > property uppercase has always done the trick. > > I've tried the following scenarios: > > * installing as an Administrator > * installing as a non-Administrator > * setting the property with a custom action > * setting the property with a Property element > * setting the property from the command line > * using the property in the Execute sequence in an immediate custom action > * setting the ALLUSERS property to "1" and installing as a > non-administrator > > I've tried it in XP, Windows 7 and Windows Server 2008. > > It always works for me without using the Secure attribute. However, I see > many sources that say the Secure attribute is needed. Can anyone show me a > scenario, with the steps to take, when this is really necessary? When not > having that attribute would cause an error? > > I appreciate any help. > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Property-Secure-when-to-use-tp4982590p4982590.html > Sent from the wix-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
