🚀 go-pugleaf

"Murray Nelson" <mnpicker@agt.net> wrote in message
news:3EA4C5ED.5050505@agt.net...
> Interesting. I wonder is there a place one can find
> some in depth information on shellexecute().

There's not much to tell about it.  You give it a filename, and it resolves
which type of file it is, based on the file extension.  Or in the case of
URLs, the protocol used.  Then it goes into the HKEY_CLASSES_ROOT section of
the Registry, looks to see if the file type is registered, and if so then
simply executes the command associated with the file type's registered verb
that is specified in the lpOperation parameter of ShellExecute().

So, for example, when executing a URL, the http protocol is registered as
follows:

    HKEY_CLASSES_ROOT\http\shell\open\command
    (Default)="F:\PROGRA~1\INTERN~2\iexplore.exe" -nohome

The URL passed to ShellExecute() will be passed to the web browser as a
command line parameter.  So, in this particular example, IE would be invoked
as such:

    F:\PROGRA~1\INTERN~2\iexplore.exe -nohome "http://theurl.com"

At startup, IE can look to see if it was passed any command-line parameters,
and if so then process them accordingly.

> Like included libraries?

ShellExecute(), like its name implies, is part of the OS Shell itself,
available in shell32.dll.


Gambit