Windows Processes

Which are the better functions to be called under windows to create processes , test exit code, interprocess communication/syncronization?

use the API calls provided. check MSDN for the specific functions. It is nto usually beneficial to start additionl processes, just use threads.

Originally Posted by abachler

use the API calls provided. check MSDN for the specific functions. It is nto usually beneficial to start additionl processes, just use threads.

yes I agree
usually it is just better to use threads
But to execute an externally provided (and ready) .exe ..

MSDN is your reference for the Win32 API and associated MS libraries.
http://msdn.microsoft.com/en-us/libr...84(VS.85).aspx

CreateProcess() is the OS interface for process creation. IPC on windows includes shared memory, sockets, named pipes, mail slots, and few others.
http://msdn.microsoft.com/en-us/libr...74(VS.85).aspx

gg

Originally Posted by Codeplug

MSDN is your reference for the Win32 API and associated MS libraries.
http://msdn.microsoft.com/en-us/libr...84(VS.85).aspx

CreateProcess() is the OS interface for process creation. IPC on windows includes shared memory, sockets, named pipes, mail slots, and few others.
http://msdn.microsoft.com/en-us/libr...74(VS.85).aspx

gg

thank you
quite enough stuff to study (-;

Sending messages, WM_COPYDATA in particular, can be used for IPC as well.

Originally Posted by mynickmynick

yes I agree
usually it is just better to use threads
But to execute an externally provided (and ready) .exe ..

If you are doign software development, it really is necessary that the customer provide you witht eh existing source code when they want features added to an application. Using one program to run another 3rd party program is generalyl considered a kludge. There are API coimmands to handle it since many applications like auto-patchers require such functionality.

Originally Posted by abachler

If you are doign software development, it really is necessary that the customer provide you witht eh existing source code when they want features added to an application. Using one program to run another 3rd party program is generalyl considered a kludge. There are API coimmands to handle it since many applications like auto-patchers require such functionality.

yes I quite agree