ShellExecuteEx

[SFSxOI]

Does anyone have any problems with using the ShellExecuteEx API on 64 bit Windows Vista or Windows 7 systems?

[lexvictory]

what problems are you having? it works fine here on Win 7

[SFSxOI]

what problems are you having? it works fine here on Win 7

not really a problem, just a slightly different operation behavior in a 64 bit system that sort of suprised me. In "sketching" out some code today for a project I used this:

Code: Select all

Procedure Elevated_Cmd(app_dir.s, app_name.s)
AppVerb$ = "runas"
AppName$ = app_name
AppDir$ = app_dir

shExecInfo.SHELLEXECUTEINFO 
shExecInfo\cbSize=SizeOf(SHELLEXECUTEINFO) 
shExecInfo\fMask=#Null 
shExecInfo\hwnd=#Null 
shExecInfo\lpVerb=@AppVerb$
shExecInfo\lpFile=@AppName$ 
shExecInfo\lpDirectory=@AppDir$
shExecInfo\nShow=#SW_NORMAL

exe.i = ShellExecuteEx_(@shExecInfo)

ProcedureReturn exe

EndProcedure

In experimenting some while working out a few things i accidently passed the full path to the .exe to the above procedure, and it worked. Before today I had worked on things using that with just 32 bit, but this project was intended to operate on 64 bit and 32 bit. In the past 32 bit usage in Vista and Windows 7 I passed just the .exe name to the app_name.s parameter and it worked fine, but when I pass just the app name here it didn't work in the 64 bit Windows 7, but when I passed the full path (accidently) it worked fine. So I was just wondering, seeing as I had not messed with doing anything with 64 bit in mind before, if there was some sort of difference i'm not aware of that would cause this behavior.

[Rescator]

Depends on the exe you try to run.
For example a 32bit program can run a 32it or 64bit exe.
but I'm not so sure if a 64bit program will call a 32bit exe as I assume that 64bit windows does not search the 32bit exe system path?
But it will let search the 32bit and 64bit system paths on 32bit for compatibility reasons I assume?
Just a guess though, ever really tested such behavior.