shellexecute() new feature

[lookinmyeyes]

I have code that i would use runasset() to change the profile that a program will run under with version 3.10,
i used shellexecute() after runasset() to elevate the shellexecute to specifig user privileges.
i know i can use
ShellExecute("rundll32.exe", "shell32.dll, OpenAs_RunDLL " & $filename, "", "runas")

to get the windows run as box, but this requires to enter username and password after they have been entered into the autoit code to start up the application.

I am suggesting something like shellexecuteas() or something similar to runas() so that we can specify in the code username and password to use.

[TicketCleanup]

Automatic ticket cleanup.

[Valik]

Replying to lookinmyeyes:

I have code that i would use runasset() to change the profile that a program will run under with version 3.10,
i used shellexecute() after runasset() to elevate the shellexecute to specifig user privileges.

You must have a magical version of AutoIt, then. What you suggest just simply was not implemented that way. You were still running the script in the context of the caller, not the callee you thought. In other words, removing RunAsSet() did not remove any functionality some of you think you had.

i know i can use
ShellExecute("rundll32.exe", "shell32.dll, OpenAs_RunDLL " & $filename, "", "runas")

to get the windows run as box, but this requires to enter username and password after they have been entered into the autoit code to start up the application.

I am suggesting something like shellexecuteas() or something similar to runas() so that we can specify in the code username and password to use.

This is not going to happen. The API does not support it. What you can do, however, is use the /AutoIt3ExecuteLine feature of AutoIt. You can leverage that along with RunAs() to invoke ShellExecute() from an instance of AutoIt running as the user you want. The code would be something like:

Local Const $sAutoItExe = "Some Place UserB has access to"
Local Const $sCmd = '"ShellExecute(blah blah blah)"'
FileCopy(@AutoItExe, $sAutoItExe)
RunAsWait("UserB", "UserBpass", @ComputerName, 0, $sAutoItExe & " /AutoIt3ExecuteLine " & $sCmd)
FileDelete($sAutoItExe)

You will have some trouble with quotes, it's finicky getting them right since you must pass valid AutoIt syntax to /AutoIt3ExecuteLine and you must pass it as a SINGLE parameter (meaning the item has to be quoted itself). But basically you copy the AutoIt interpreter (A compiled script is fine) to a location UserB can access. Then you run that interpreter and have it execute your ShellExecute() line under the context of UserB. Then you clean up.