Yes. Binary table.
EXE custom actions should be a last resort, however, and is a bad user
experience (you would have two prompts-for-elevation). Generating the
certificate and inserting its details into the appropriate table during the
execute sequence would be more reliable, easier to rollback, and a better user
experience.
-Blair
> From: kaize...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Date: Sun, 24 Nov 2013 17:57:57 +1100
> Subject: Re: [WiX-users] Calling CustomAction which requires Elevated
>
> Ok.. so it seems staying in the MSI process and getting elevated privileges
> just isn't possible, which explains why this doesn't work at all (since it's
> using the 'immediate' execution, which runs in the MSI process)..
>
> Next plan... I'd like to create an executable which will perform this work,
> and also elevate itself if required.
> I would like to get the WIX UI immediate action to execute this EXE (out of
> process). Is this possible?
>
> Is there any way of embedding a binary exe into the MSI, so that it can be
> called, without it actually getting installed?
>
>
> Regards,
> Bevan
>
> >
> >Date: Sat, 23 Nov 2013 18:34:55 +1100
> >From: Bevan Weiss <kaize...@hotmail.com>
> >
> >Hi all,
> >
> >I'm trying to create a WIX installer which allows a user to select a
> certificate to use for a Web Site SSL binding.
> >However, if they don't have a valid certificate installed yet (just looking
> in the Local Machine, My certificate store) then I'd like them to be able to
> generate a Self-Signed Certificate from within the UI.
> >
> >I've got a CA which will happily generate a Self-Signed Certificate,
> however I don't seem to be able to get the elevated privileges unless I
> actually execute the MSI from an elevated command line.
> >I've tried the following:
> >1) Setting the ElevationShield="yes" on the PushButton which calls the CA
> (this looks spot on.. but doesn't appear to change anything regards actually
> Elevation status)
> >2) Setting the Impersonate="no" setting on the CustomAction (which
> references the CA .dll that I've created).
> >
> >Is there anything more obvious that I'm missing?
> >I do have InstallPrivileges="elevated" set on the overall Package.. and
> InstallScope="perMachine"
> >
> >I'm sure some of you have even done this successfully before.. would love
> to know how.
> >
> >
> >Regards,
> >Bevan Weiss
> >*****
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
