Thanks Phil,
It's an installer for Web Services.  So there really isn't any 'first run'
or anything at all really...
Install, and then it should just operate for eternity.

Is it possible to put elevated privileges as a package condition?  Then if
the MSI is run without them I could just error out and prompt the user to
launch 'as Administrator'.
Not the nicest solution, but it's a possible work-around.  They would need
Admin credentials to perform the install anyway...



-----Original Message-----
Date: Sat, 23 Nov 2013 11:19:11 -0800
From: Phil Wilson <phildgwil...@gmail.com>
Subject: Re: [WiX-users] Calling CustomAction which requires Elevated
        Privileges from UI PushButton

The problem is that the UI sequence runs with installing user credentials,
so if elevation is required it must come at launch time. If you were to
shell execute an external process that asked for elevation it should work
but the workflow would probably be terrible.
This is one of those tasks that should be encouraged to be part of
configuration done by the app at first run, by an administrator, if that's
possible in your scenario - some things like this just aren't very easy in
the UAC world.

Phil Wilson


On Fri, Nov 22, 2013 at 11:34 PM, Bevan Weiss <kaize...@hotmail.com> wrote:

> 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.

------------------------------------------------------------------------------
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

Reply via email to