skipinfo can't be blocking because wyUpdate may update itself and/or it may request UAC privileges. Either case causes wyUpdate to launch a new instance of itself.
To start your app after an update see: Executing files in your update
Can I wait for "wyUpdate.exe /skipinfo" to complete?
Hi. Trying to run wyUpdate.exe in "stand alone" mode - ie. I have a simple start.cmd batch file with:
@ECHO OFFwyUpdate.exe /quickcheck /justcheck /noerrIF ERRORLEVEL 2 GOTO UPDATEIF ERRORLEVEL 0 GOTO START
:UPDATEwyUpdate.exe /skipinfo
:STARTstart /B myProgram.exe
The first call to wyUpdate.exe is a blocking call - we await the exit code and acts correspondingly. Fine.The second call to wyUpdate.exe seems to return almost immediately, and hence myProgram often starts, BEFORE the wyUpdate update/install process is complete.
Any ideas how to avoid this? We need the update+install to complete BEFORE starting the program itself.
Regards,Thomas
Ok, thank you for a very quick reply. I think that will work fine - I didn't see the option to execute a file after update, so thanks for that "pointer".
Of course, we then need to repeat this step for every release, I guess - but that is not a big deal. Should we forget that step one day, the end result is just that the user will have to start our application with another click after update.
Regards,Thomas