Updater /silent -nofreqcheck

[karlf]

Hello,

I am trying to allow for my program to call updater.exe each time it starts silently. I am aware of the /silent option, however in the documentation here:

http://www.advancedinstaller.com/user-g ... dater.html

it says that the -nofreqcheck switch is only valid with the /silentall and /silentcritical options. However, in a reply to this forum post:

http://www.advancedinstaller.com/forums ... hp?t=28718

it is said that -nofreqcheck can be used with /silent.

My first question I am trying to have answered, is if this is actually the case, because when I call "updater.exe /silent -nofreqcheck" I get no results, nothing comes back saying there is an update available. This is after the user has set the updater to not look for updates again until tomorrow. However when I call just "updater.exe", it finds the update no problem. It seems as though the -nofreqcheck is not working with the /silent option. If I call "updater.exe /silentall -nofreqcheck", then I get the "checking for updates" dialog as well as a new update available.

My second question is, if the user decides to tell the updater to not check for anymore updates until tomorrow, is there a way to reset that value? I know about the /configure option, but it doesn't seem to allow when the next check frequency will be. This would be useful in testing scenarios, because currently the person responsible for testing the program needs to uninstall and re-install to revert that value back to anytime before the next day.

Thanks for the great support

[Eusebiu]

Hi,

Indeed, the "/silent" command line does not work with the "-nofreqcheck" switch. I made a mistake when I wrote that in the other thread, but I modified that and wrote the correct solution. Thank you for bringing this to our attention.

My first question I am trying to have answered, is if this is actually the case, because when I call "updater.exe /silent -nofreqcheck" I get no results, nothing comes back saying there is an update available. This is after the user has set the updater to not look for updates again until tomorrow. However when I call just "updater.exe", it finds the update no problem. It seems as though the -nofreqcheck is not working with the /silent option. If I call "updater.exe /silentall -nofreqcheck", then I get the "checking for updates" dialog as well as a new update available.

In order to have no user interface for the updater and also no frequency check, you can use the "/checknow -minuseractions" command line.

My second question is, if the user decides to tell the updater to not check for anymore updates until tomorrow, is there a way to reset that value? I know about the /configure option, but it doesn't seem to allow when the next check frequency will be. This would be useful in testing scenarios, because currently the person responsible for testing the program needs to uninstall and re-install to revert that value back to anytime before the next day.

In order to change that, you can go to the location where the updater executable was installed, open the "updater.ini" file and modify the value of the "CheckFrequency" attribute.

Best regards,
Eusebiu

[karlf]

Hello,

Thanks for the quick response, I appreciate it. Is it possible that you could post a sample updater.ini? I don't have an entry in mine for CheckFrequency. This could possibly be because I have my update check frequency set to 0 days and I don't have the "Use check frequency" checkbox checked? My ini file looks like this:

[General]
AppDir=C:\Program Files (x86)\DCI\DigiTrak LWD Bundle\
ID={49C00085-54A6-4C17-ACC9-929A458E27F6}
ApplicationName=DigiTrak LWD Bundle
CompanyName=DCI
ApplicationVersion=3.0.27882
DefaultCommandLine=/checknow
DownloadsFolder=C:\ProgramData\DCI\DigiTrak LWD Bundle\updates\
Flags=PerMachine|ShowConfigOptionsButton
URL=DOWNLOAD_URL_HERE

[Eusebiu]

Hi,

Yes, the check frequency does not apply when the "/checknow" command is used for the updater. So, if you use the "/checknow -minuseractions" command line that I suggested, you will not need to work with the check frequency.

If you use the "/silent" or "/silentall" commands, a check frequency will be applied and the "updater.ini" file will look as below:

• [General]
  AppDir=C:\Program Files\Your Company\Your Application\
  ID={F4678F55-C891-489D-A56A-0982A64BC640}
  ApplicationName=Your Application
  CompanyName=Your Company
  ApplicationVersion=1.0.0
  DefaultCommandLine=/silent
  CheckFrequency=2
  DownloadsFolder=C:\ProgramData\Your Company\Your Application\updates\
  Flags=PerMachine|ShowConfigOptionsButton
  URL=DOWNLOAD_URL

Best regards,
Eusebiu