C / C++ / MFC

Doc Lobster12-Jun-07 22:34

Doc Lobster

12-Jun-07 22:34

Maybe this helps:

http://www.codeproject.com/threads/sendmsg.asp?df=100&forumid=120&exp=0&select=698959[^]

That won't work with ShellExecute but with ShellExecuteEx which may provide you with the process handle.

Naveen13-Jun-07 0:22

13-Jun-07 0:22

If you use the ShellExecuteEx() function, you will get the HANDLE of the process. So atleast you will be able to call TerminateProcess() function.

nave

[OpenedFileFinder]

Russell^'13-Jun-07 1:46

Russell^'

13-Jun-07 1:46

It works

This is my code (if someone needs it):

// Fill the structure
SHELLEXECUTEINFO ShellExecuteInfo;
ShellExecuteInfo.cbSize = sizeof(SHELLEXECUTEINFO);
ShellExecuteInfo.fMask = SEE_MASK_NOCLOSEPROCESS;
ShellExecuteInfo.hwnd = NULL;
ShellExecuteInfo.lpVerb = NULL;
ShellExecuteInfo.lpFile = "notepad.exe";
ShellExecuteInfo.lpParameters = "";
ShellExecuteInfo.lpDirectory = NULL;
ShellExecuteInfo.nShow = SW_SHOW;
ShellExecuteInfo.hInstApp = NULL;

// Open the application
ShellExecuteEx(&ShellExecuteInfo);

// Wait some seconds
Sleep(10000);

// Terminate the process
TerminateProcess(ShellExecuteInfo.hProcess, NULL);

Thanks

Russell

Stephen Hewitt13-Jun-07 13:47

13-Jun-07 13:47

_Russell_ wrote:
It works

Does it?....
Here's a quote from MSDN on TerminateProcess:

The TerminateProcess function is used to unconditionally cause a process to exit. The state of global data maintained by dynamic-link libraries (DLLs) may be compromised if TerminateProcess is used rather than ExitProcess.

ExitProcess is of no use to you however as it exits the calling process! Calling TerminateProcess like you are is, in general, dangerous and unpredictable. For example, the process could be half way through updating a file and terminating it will result in data corruption. Another example, as eluded to by MSDN, is if the DLL uses shared memory: in this case the corruption will spread to other processes using the same DLL. TerminateProcess in only meant as a last resort: you can’t make reliable software that uses it as the primary mechanism to get a process to exit.

Steve

Stephen Hewitt13-Jun-07 13:49

13-Jun-07 13:49

Here's a quote from MSDN on TerminateProcess:

ExitProcess is of no use however as it exits the calling process! Calling TerminateProcess like you suggest is, in general, dangerous and unpredictable. For example, the process could be half way through updating a file and terminating it will result in data corruption. Another example, as eluded to by MSDN, is if the DLL uses shared memory: in this case the corruption will spread to other processes using the same DLL. TerminateProcess in only meant as a last resort: you can’t make reliable software that uses it as the primary mechanism to get a process to exit.

Steve

Naveen13-Jun-07 14:03

13-Jun-07 14:03

Ya I know the risk. But didnt find any other way.

nave

[OpenedFileFinder]

Stephen Hewitt13-Jun-07 14:09

13-Jun-07 14:09

Naveen.R wrote:
Ya I know the risk. But didnt find any other way.

But does (did) the OP?

Steve

Naveen13-Jun-07 14:10

13-Jun-07 14:10

sorry 'OP' means?

nave

[OpenedFileFinder]

Stephen Hewitt13-Jun-07 14:13

13-Jun-07 14:13

The Original Poster.

Steve

Naveen13-Jun-07 14:23