457431ab5b
We use a named pipe to communicate between the client (i.e. the process that called MsiInstallProduct() and the custom action server. The naïve approach has the client send custom action GUIDs to the server and the server send back the results of executing the action, but this fails in the case of nested custom actions, so instead we send back handles of threads for the client to wait on. Signed-off-by: Zebediah Figura <z.figura12@gmail.com> Signed-off-by: Hans Leidekker <hans@codeweavers.com> Signed-off-by: Alexandre Julliard <julliard@winehq.org> |
||
|---|---|---|
| .. | ||
| Makefile.in | ||
| msiexec.c | ||
| msiexec.ico | ||
| msiexec.man.in | ||
| msiexec.svg | ||
| rsrc.rc | ||
| service.c | ||
