There are two ways in which I want to run the Updater:
1) If the user choose "Check for an Update" from our menu. I do not want it to be affected by the frequency check that is built into Updater.exe. So I'm specifying /checknow and that works fine.
2) When my application starts, I decide if enough time has passed since the last check and, if so, I call the Updater. My decision is based on a frequency that is specified by the user in my application. So again, I do not want it to be affected by the built-in frequency-check. I want it to check every time that I call Updater.exe.
In this case, if an update is available, I want it to prompt the user, etc., just as in the case above. But if there is no update available, I want it to say NOTHING. I don't want a "Your software is up-to-date" dialog or anything else.
So I thought that I should use /checknow /silent. But that still gives me a "Your software is up-to-date" dialog.
According to the help file, /silent by itself is subject to "the interval specified by the user".
But -nofreqcheck" can apparently only be used with the /silentall and /silentcritical.
I would I use /justcheck and, if there is an update, I'd call it again with /checknow. But I'm calling Updater.exe through ShellExecuteA in my environment and I don't seem to have access to the return code.
Is there another way to get Updater.exe to be completely silent when there is no update and to prompt the user when there is one?
Thanks.
FOLLOW US
Get the latest news in Application Packaging