I tried this and the installer failed with error code 2762: DEBUG: Error 2762: Unable to schedule operation. The action must be scheduled between InstallInitialize and InstallFinalize. I guess I can launch this before InstallFinalize and have an IPC mechanism that would launch the configuration tool.
I emphasize that the config tool is called in ExitDlg, if the user has selected the launch of this tool. ----- Original Message ----- From: "Rob Mensching" <[EMAIL PROTECTED]> To: "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> Sent: Monday, December 01, 2008 5:58 PM Subject: Re: [WiX-users] elevating twice > You'd have to launch your configuration tool as a deferred async > CustomAction. > > -----Original Message----- > From: Calin Iaru [mailto:[EMAIL PROTECTED] > Sent: Monday, December 01, 2008 06:54 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] elevating twice > > If UAC is enabled, then my MSI will require one elevation prompt during > installation. This is acceptable, since registry keys are written and > other > components such as drivers are installed. What I would like to do is to > circumvent a second elevation when the MSI file is scheduled to launch an > image at the end of the installation. Here's the use case: > - the user installs a feature that requires configuration > - the configuration tool is launched at the end of the installation if > the > user marks that option > - the configuration tool needs to write files in the system directory > If CreateProcess is called in the custom action, then the installer will > fail to launch due to insufficient privileges. If ShellExecute is called, > then the process can be launched only if the user confirms a second UAC. > > My question is: can I bypass this second elevation and make the process > run > from the context of the first elevation - ie. the context of the msiexec > process that is running with elevated installation privileges? I expect > not > since that msiexec or dllhost has a limited scope. The setup uses version > 2.0.4820.0 of WiX. > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
