Try this... the user will see a UAC prompt, same as if the application
was manually launched. There's no way around this, but our users have
never complained.
>> So what is the conclusion? That what I am trying is basically impossible?
> MSI will not launch an elevated process except as a deferred custom
> action and you can't use those from the UI.
I read that as a "yes".
So, what is my options then? I will of course attempt the solution that
Palb
On 7/7/2010 8:05 AM, Thomas Due wrote:
> So what is the conclusion? That what I am trying is basically impossible?
>
MSI will not launch an elevated process except as a deferred custom
action and you can't use those from the UI.
--
sig://boB
http://joyofsetup.com/
Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-
From: Thomas Due [mailto:t...@scanvaegt.dk]
Sent: 07 July 2010 13:05
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problems launching an application on finish
So what is the conclusion? T
y as to not allow UAC to be invoked, and the
application's elevation manifest prevents execution.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, July 05, 2010 4:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-use
elevation manifest prevents execution.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, July 05, 2010 4:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problems launching an application on finish
Try adding the I
Try adding the Impersonate attribute with value "no" to your CustomAction
element. You may also want to change the Execute attribute to "commit" or
"deferred". See ->
http://wix.sourceforge.net/manual-wix3/wix_xsd_customaction.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44
7 matches
Mail list logo
