🚀 go-pugleaf

Thanks. That is ALMOST the process I have taken. Sicne I didn't write the
setup program, I actually wrote another "program" that I launch from my
application that I do pass the current process id and then it runs the
Setup.exe when it can.

I was just wondering if there was a hidden API command I didn't know about.

Regards,

Shane

"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:jqehf0d0r75u75ueq75mmlfd6fauqc4ula@4ax.com...
> Shane Stump wrote:
>
> >I am in the process of writing a component for my applications that check
/
> >download a new version of the program. The actual file that is downloaded
is
> >a setup program. Can anyone recommend the BEST way to shutdown my current
> >running application and launch the downloaded the Setup.exe?
>
> Well, it would seem like using CreateProcess on Setup.exe, then
> immediately terminating would do the job.
> But there is a race condition. Not so significant if Setup needs to
> unpack before it installs....but still...
>
> One way is for the application to use GetCurrentProcessId(), convert
> the ID to a string and pass that as a parameter to Setup.
>
> If Setup doesn't see the parameter, then it was manually started, so
> just go ahead and install.
> If Setup sees the parameter, it waits for the caller to close:
>
> ProcessID = atol(argv[1]);
> OldProcess = OpenProcess(PROCESS_QUERY_INFORMATION, FALSE, ProcessID);
> if( OldProcess != NULL )
> { WaitForSingleObject(OldProcess, INFINITE);
> CloseHandle(OldProcess);
> }
>
>