ShellExecute

[jose.luis]

Hola,
Dos preguntas:
a. Cual diferencia hay entre ShellExecute y ShellExecuteEx aparte del valor
de retorno?
b. Con ShellExecute lanzo una aplicación (CESARFTP) en modo hide (último
parámetro a SW_HIDE). No se por cual motivo me aparece una ventana de la
consola de MSDOS que desaparece cuando se ha cargado el CesarFtp. ¿Como
puedo evitar que aparezca esa ventana DOS?
Saludos y gracias,
José Luis Capel

[ignacio]

ShellExecute Function
------------------------------------------------------------ --------------------
Performs an operation on a specified file.
Syntax
HINSTANCE ShellExecute( HWND hwnd,
LPCTSTR lpOperation,
LPCTSTR lpFile,
LPCTSTR lpParameters,
LPCTSTR lpDirectory,
INT nShowCmd
);Parameters
hwnd
[in] Handle to the owner window used for displaying a user interface
(UI) or error messages. This value can be NULL if the operation is not
associated with a window.
lpOperation
[in] Pointer to a null-terminated string, referred to in this case as a
verb, that specifies the action to be performed. The set of available verbs
depends on the particular file or folder. Generally, the actions available
from an object's shortcut menu are available verbs. For more information
about verbs and their availability, see Object Verbs. See Extending Shortcut
Menus for further discussion of shortcut menus. The following verbs are
commonly used.
edit
Launches an editor and opens the document for editing. If lpFile is
not a document file, the function will fail.
explore
Explores the folder specified by lpFile.
find
Initiates a search starting from the specified directory.
open
Opens the file specified by the lpFile parameter. The file can be an
executable file, a document file, or a folder.
print
Prints the document file specified by lpFile. If lpFile is not a
document file, the function will fail.
NULL
For systems prior to Microsoft Windows 2000, the default verb is used
if it is valid and available in the registry. If not, the "open" verb is
used.
For Windows 2000 and later systems, the default verb is used if
available. If not, the "open" verb is used. If neither verb is available,
the system uses the first verb listed in the registry.
lpFile
[in] Pointer to a null-terminated string that specifies the file or
object on which to execute the specified verb. To specify a Shell namespace
object, pass the fully qualified parse name. Note that not all verbs are
supported on all objects. For example, not all document types support the
"print" verb.
lpParameters
[in] If the lpFile parameter specifies an executable file, lpParameters
is a pointer to a null-terminated string that specifies the parameters to be
passed to the application. The format of this string is determined by the
verb that is to be invoked. If lpFile specifies a document file,
lpParameters should be NULL.
lpDirectory
[in] Pointer to a null-terminated string that specifies the default
directory.
nShowCmd
[in] Flags that specify how an application is to be displayed when it is
opened. If lpFile specifies a document file, the flag is simply passed to
the associated application. It is up to the application to decide how to
handle it.
SW_HIDE
Hides the window and activates another window.
SW_MAXIMIZE
Maximizes the specified window.
SW_MINIMIZE
Minimizes the specified window and activates the next top-level window
in the z-order.
SW_RESTORE
Activates and displays the window. If the window is minimized or
maximized, Windows restores it to its original size and position. An
application should specify this flag when restoring a minimized window.
SW_SHOW
Activates the window and displays it in its current size and position.
SW_SHOWDEFAULT
Sets the show state based on the SW_ flag specified in the STARTUPINFO
structure passed to the CreateProcess function by the program that started
the application. An application should call ShowWindow with this flag to set
the initial show state of its main window.
SW_SHOWMAXIMIZED
Activates the window and displays it as a maximized window.
SW_SHOWMINIMIZED
Activates the window and displays it as a minimized window.
SW_SHOWMINNOACTIVE
Displays the window as a minimized window. The active window remains
active.
SW_SHOWNA
Displays the window in its current state. The active window remains
active.
SW_SHOWNOACTIVATE
Displays a window in its most recent size and position. The active
window remains active.
SW_SHOWNORMAL
Activates and displays a window. If the window is minimized or
maximized, Windows restores it to its original size and position. An
application should specify this flag when displaying the window for the
first time.
Return Value
Returns a value greater than 32 if successful, or an error value that is
less than or equal to 32 otherwise. The following table lists the error
values. The return value is cast as an HINSTANCE for backward compatibility
with 16-bit Windows applications. It is not a true HINSTANCE, however. The
only thing that can be done with the returned HINSTANCE is to cast it to an
int and compare it with the value 32 or one of the error codes below.
0 The operating system is out of memory or resources.
ERROR_FILE_NOT_FOUND The specified file was not found.
ERROR_PATH_NOT_FOUND The specified path was not found.
ERROR_BAD_FORMAT The .exe file is invalid (non-Microsoft Win32 .exe
or error in .exe image).
SE_ERR_ACCESSDENIED The operating system denied access to the
specified file.
SE_ERR_ASSOCINCOMPLETE The file name association is incomplete or
invalid.
SE_ERR_DDEBUSY The Dynamic Data Exchange (DDE) transaction could not
be completed because other DDE transactions were being processed.
SE_ERR_DDEFAIL The DDE transaction failed.
SE_ERR_DDETIMEOUT The DDE transaction could not be completed because
the request timed out.
SE_ERR_DLLNOTFOUND The specified dynamic-link library (DLL) was not
found.
SE_ERR_FNF The specified file was not found.
SE_ERR_NOASSOC There is no application associated with the given
file name extension. This error will also be returned if you attempt to
print a file that is not printable.
SE_ERR_OOM There was not enough memory to complete the operation.
SE_ERR_PNF The specified path was not found.
SE_ERR_SHARE A sharing violation occurred.
Remarks
This method allows you to execute any commands in a folder's shortcut menu
or stored in the registry.
To open a folder, use either of the following calls:
ShellExecute(handle, NULL, <fully_qualified_path_to_folder>, NULL, NULL,
SW_SHOWNORMAL);
or
ShellExecute(handle, "open", <fully_qualified_path_to_folder>, NULL, NULL,
SW_SHOWNORMAL);
To explore a folder, use:
ShellExecute(handle, "explore", <fully_qualified_path_to_folder>, NULL,
NULL, SW_SHOWNORMAL);
To launch the Shell's Find utility for a directory, use:
ShellExecute(handle, "find", <fully_qualified_path_to_folder>, NULL, NULL,
0);
If lpOperation is NULL, the function opens the file specified by lpFile.
If lpOperation is "open" or "explore", the function attempts to open or
explore the folder.
To obtain information about the application that is launched as a result
of calling ShellExecute, use ShellExecuteEx.
Note The Launch folder windows in a separate process setting in Folder
Options affects ShellExecute. If that option is disabled (the default
setting), ShellExecute uses an open Explorer window rather than launch a new
one. If no Explorer window is open, ShellExecute launches a new one.
Windows 95/98/Me: ShellExecute is supported by the Microsoft Layer for
Unicode. To use this, you must add certain files to your application, as
outlined in Microsoft Layer for Unicode on Windows 95/98/Me Systems.
Function Information
Minimum DLL Version shell32.dll version 3.51 or later
Custom Implementation No
Header shellapi.h
Import library shell32.lib
Minimum operating systems Windows NT 3.1, Windows 95
Unicode Implemented as ANSI and Unicode versions.
See Also
IShellExecuteHook
------------------------------------------------------------ --------------------
© 2005 Microsoft Corporation. All rights reserved.
ShellExecuteEx Function
------------------------------------------------------------ --------------------
Performs an action on a file.
Syntax
BOOL ShellExecuteEx( LPSHELLEXECUTEINFO lpExecInfo
);Parameters
lpExecInfo
Address of a SHELLEXECUTEINFO structure that contains and receives
information about the application being executed.
Return Value
Returns TRUE if successful, or FALSE otherwise. Call GetLastError for
error information.
Remarks
With multiple monitors, if you specify an HWND and set the lpVerb member
of lpExecInfo to "Properties", any windows created by ShellExecuteEx may not
appear in the correct position.
If the function succeeds, it sets the hInstApp member of the
SHELLEXECUTEINFO structure to a value greater than 32. If the function
fails, hInstApp is set to the SE_ERR_XXX error value that best indicates the
cause of the failure. Although hInstApp is declared as an HINSTANCE for
compatibility with 16-bit Microsoft Windows applications, it is not a true
HINSTANCE. It can only be cast to an int and compared to either 32 or the
SE_ERR_XXX error codes.
Note The SE_ERR_XXX error values are provided for compatibility with
ShellExecute. To retrieve more accurate error information, use GetLastError.
It may return one of the following values:
Error Description
ERROR_FILE_NOT_FOUND The specified file was not found.
ERROR_PATH_NOT_FOUND The specified path was not found.
ERROR_DDE_FAIL The Dynamic Data Exchange (DDE) transaction failed.
ERROR_NO_ASSOCIATION There is no application associated with the
given file name extension.
ERROR_ACCESS_DENIED Access to the specified file is denied.
ERROR_DLL_NOT_FOUND One of the library files necessary to run the
application can't be found.
ERROR_CANCELLED The function prompted the user for additional
information, but the user canceled the request.
ERROR_NOT_ENOUGH_MEMORY There is not enough memory to perform the
specified action.
ERROR_SHARING_VIOLATION A sharing violation occurred.
Windows 95/98/Me: ShellExecuteEx is supported by the Microsoft Layer for
Unicode. To use this, you must add certain files to your application, as
outlined in Microsoft Layer for Unicode on Windows 95/98/Me Systems.
Function Information
Minimum DLL Version shell32.dll version 3.51 or later
Custom Implementation No
Header shellapi.h
Import library shell32.lib
Minimum operating systems Windows NT 4.0, Windows 95
Unicode Implemented as ANSI and Unicode versions.
See Also
IShellExecuteHook
------------------------------------------------------------ --------------------
© 2005 Microsoft Corporation. All rights reserved.
"José Luis Capel" <jose.luis@iaicom.com> escribió en el mensaje
news:[email=44aaaaae@news.xailer.com...]44aaaaae@news.xailer.com...[/email]
> Hola,
>
> Dos preguntas:
>
> a. Cual diferencia hay entre ShellExecute y ShellExecuteEx aparte del
> valor de retorno?
>
> b. Con ShellExecute lanzo una aplicación (CESARFTP) en modo hide (último
> parámetro a SW_HIDE). No se por cual motivo me aparece una ventana de la
> consola de MSDOS que desaparece cuando se ha cargado el CesarFtp. ¿Como
> puedo evitar que aparezca esa ventana DOS?
>
> Saludos y gracias,
> José Luis Capel
>

[jose.luis]

Ignacio,
Gracias tu respuesta. Me refería a las funciones de Xailer:
Funciones de DLLs y ejecución
Nombre
Execute
IsRunning
KillProcess
Funciones del API de Windows accesibles desde Xailer:
· DllFileOS( cDll ) --> cFileOS
· DllFileType( cDll ) --> cFileType
· DllFileVersion( cDll ) --> cVersion
· DllVersion( cDll ) --> { nHiMS, nLoMS, nHiLS, nLoLS, nFileOS,
nFileType }
· DllVersionBuild( cDll ) --> nBuild
· DllVersionMajor( cDll ) --> nMajor
· DllVersionMinor( cDll ) --> nMinor
· DllVersionRelease( cDll ) --> nRelease
· FreeLibrary( hLib ) --> nSuccess
· LoadLibrary( cDLL ) --> hLib
· ShellExecute( hWnd, cOper, cFile, cParam, cDir, nShowMode ) -->
nReturn
· ShellExecuteEx( hWnd, cFile, cOper, cParam, cDir, nShowMode ) -->
lSuccess
· WinExec( cFile, nMode ) --> nError
Tanto ShellExecute como ShellExecuteEx tienen los mismo parámetros y la
diferencia es el valor de retorno. Entonces mi cuestión es si hay alguna
diferencia en el uso de una u otra (aparte del valor de retorno).
Saludos y gracias,
José Luis Capel
"José Luis Capel" <jose.luis@iaicom.com> escribió en el mensaje
news:[email=44aaaaae@news.xailer.com...]44aaaaae@news.xailer.com...[/email]
> Hola,
>
> Dos preguntas:
>
> a. Cual diferencia hay entre ShellExecute y ShellExecuteEx aparte del
> valor
> de retorno?
>
> b. Con ShellExecute lanzo una aplicación (CESARFTP) en modo hide (último
> parámetro a SW_HIDE). No se por cual motivo me aparece una ventana de la
> consola de MSDOS que desaparece cuando se ha cargado el CesarFtp. ¿Como
> puedo evitar que aparezca esa ventana DOS?
>
> Saludos y gracias,
> José Luis Capel
>
>


Attached files

[jfgimenez]

José Luis,
Execute() utiliza la función del API CreateProcess(), mientras que
ShellExecute[Ex] son "wrappers" al API.
¿Has probado a lanzar CesarFPT con Execute()?
--
Un saludo,
José F. Giménez
http://www.xailer.com

[jose.luis]

José,
>
> Execute() utiliza la función del API CreateProcess(), mientras que
> ShellExecute[Ex] son "wrappers" al API.
Gracias por tu respuesta.
>
> ¿Has probado a lanzar CesarFPT con Execute()?
>
No, no lo he probado por que según veo en la documentación, no hay forma de
indicarle al proceso que se ejecute 'HIDE'. En mi caso me interesa que no
se vea la pantalla del CesarFTP (ni tampoco que se quede detrás de ninguna
otra ventana).
Saludos,
José Luis Capel

[ignacio]

Jose Luis,
WinExec() recibe como segundo parametro la forma de visualización de la
ventana. Intenta pasarle un SW_HIDE. De la misma forma ShellExecute() recibe
igualmente ese mismo parametro pero en la posición 6.
Saludos,
"José Luis Capel" <jose.luis@iaicom.com> escribió en el mensaje
news:44ab7fa4$[email=1@news.xailer.com...]1@news.xailer.com...[/email]
> José,
>
>>
>> Execute() utiliza la función del API CreateProcess(), mientras que
>> ShellExecute[Ex] son "wrappers" al API.
>
> Gracias por tu respuesta.
>>
>> ¿Has probado a lanzar CesarFPT con Execute()?
>>
> No, no lo he probado por que según veo en la documentación, no hay forma
> de indicarle al proceso que se ejecute 'HIDE'. En mi caso me interesa que
> no se vea la pantalla del CesarFTP (ni tampoco que se quede detrás de
> ninguna otra ventana).
>
> Saludos,
> José Luis Capel
>
>
>

[jose.luis]

Ignacio,
>
> WinExec() recibe como segundo parametro la forma de visualización de la
> ventana. Intenta pasarle un SW_HIDE. De la misma forma ShellExecute()
> recibe igualmente ese mismo parametro pero en la posición 6.
>
Probaré esta función a ver tal funciona.
Saludos,
José Luis Capel