This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Any workaround to do the same thing in Installshield 12?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 19, 2008
10:21 AM
Vista and .msi files.
I have a basic MSI project, and the end product is distributed as a .msi file. In that project I have a Custom Action that executes the LaunchAppAndWait() function. However in Vista this function fails due to access privileges unless I launch the .msi via a command prompt opened as administrator and calling msiexec.
The documentation points to setting the "Required Execution Level" to Administrator in the Release configuration, but since I am distributing an .msi instead of a setup.exe, this does not apply.
Is there some configuration of LaunchAppAndWait() that I can use to have the UAC prompt that is fired when the installer starts carry over to the CustomAction? I have tried it both with and without the LAAW_OPTION_USE_SHELLEXECUTE to no avail, but I have not tried any other configuration options.
The documentation points to setting the "Required Execution Level" to Administrator in the Release configuration, but since I am distributing an .msi instead of a setup.exe, this does not apply.
Is there some configuration of LaunchAppAndWait() that I can use to have the UAC prompt that is fired when the installer starts carry over to the CustomAction? I have tried it both with and without the LAAW_OPTION_USE_SHELLEXECUTE to no avail, but I have not tried any other configuration options.
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 19, 2008
11:30 AM
Where in the sequences are you running the custom action? What are its settings (immediate vs. deferred, and all that)?
If you haven't, you might also see this fine newsletter tip from Stefan Krueger: http://www.acresso.com/webdocuments/PDF/is_vista.pdf.
If you haven't, you might also see this fine newsletter tip from Stefan Krueger: http://www.acresso.com/webdocuments/PDF/is_vista.pdf.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 19, 2008
12:38 PM
In InstallShield 2008, the LaunchApplication function was introduced. It basically replaces the LaunchAppAndWait function.
If you are using LAAW_OPTION_USE_SHELLEXECUTE on Windows Vista and you want to run the application using the full administrator account (similar to right-clicking the executable file and selecting Run As Administrator), try setting the LAAW_SHELLEXECUTEVERB to runas before using LaunchApplication in your script:
LAAW_SHELLEXECUTEVERB = "runas";
For more information on LaunchApplication, see the help.
I hope that helps.
Debbie Landers
Acresso Software
If you are using LAAW_OPTION_USE_SHELLEXECUTE on Windows Vista and you want to run the application using the full administrator account (similar to right-clicking the executable file and selecting Run As Administrator), try setting the LAAW_SHELLEXECUTEVERB to runas before using LaunchApplication in your script:
LAAW_SHELLEXECUTEVERB = "runas";
For more information on LaunchApplication, see the help.
I hope that helps.
Debbie Landers
Acresso Software
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 19, 2008
03:42 PM
Switching to LaunchApplication and using LAAW_SHELLEXECUTEVERB = "runas" did the trick. Thanks for the help.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2008
12:23 PM
We're encountering the same problem with basic MSI custom actions in Vista. We are close to upgrading to Installshield 2009, but need to release one more version of our product with Installshield 12 beforehand. I was wondering if there was a way to achieve similar functionality with IS 12? I tried setting LAAW_SHELLEXECUTEVERB, but this isn't even recognized as a keyword in IS 12.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2008
01:55 PM
I believe there is code available on InstallSite.org which shows how to call ShellExecute from InstallScript.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2008
04:01 PM
Michael -- the closest thing I found on Installsite.org was "Extended Version of LaunchAppAndWait", but it appears that this functions still uses CreateProcess at it's core, not ShellExecute, and thus would still not get us past the UAC problem in Vista.
If you (or anyone else) have a direct link to some sample code using ShellExecute that would work in Installshield 12, it would be much appreciated.
Thanks.
If you (or anyone else) have a direct link to some sample code using ShellExecute that would work in Installshield 12, it would be much appreciated.
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 17, 2008
05:57 PM
Actually, searching these forums for "ShellExecute" turns up a couple dozen posts, so that might be worthwhile. Searching the KB turns up quite a few, too.