4 replies to this topic

[Morthawt]

I am rewriting my string based hotkey program based on what I learned from the experience of writing the first one and want to slim down the user requirement to select between run vs shellexecute. From what I am reading in the manual it looks like shellexecute will do everything I need, run exe, scr, msc everything. Is there really any need for me to use Run function?

[MilesAhead]

From looking in the help it seems that Run makes it easy to do things like redirect console output of the program being run etc.. ShellExecute is very versatile. I use ShellExecute or ShellExecuteWait for pretty much everything.

Edited by MilesAhead, 27 April 2012 - 08:42 PM.

[Morthawt]

Ok cool, I was going to write in a detection of the extension and decide which to use. But might as well use shell since I can still use parameters in the separate field. Thanks

[BrewManNH]

One of the reasons to use Run over ShellExecute is that Run returns the PID of the program being run, while shellexecute only returns 1 or 0. Another reason to use Run is if you need to read the stdout/stderror streams of a program, such as a DIR command or a program that outputs data to the command window like Xcopy or RoboCopy. If you don't need these, then ShellExecute should work most of the time.

[Morthawt]

Well so far its working perfectly in the new version.