+ Reply to Thread
Results 1 to 2 of 2

Thread: Automatic Wupdate operation.

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Automatic Wupdate operation.

    We have converted now all nine of our products from Installshield and INNO to Setup Builder. They all work better now!

    A question about automatic running of Wupdate. In our programs we have added a menu option to check for updates. When the user clicks that option, we check to see if their Maintenance Subscription is current. If so, we run Wupdate and if not, we put up a screen that encourages them to renew.

    However, we also set Wupdate to run automatically every 15 days. Does automatic running also check for a current Maintenance Subscription? If not, then we will build our own 15 day checker into our programs and only run wudate silently if their subscription is current.

    Is there a way to have this be automatic?

    -CMS Software-

  2. #2
    Join Date
    Mar 2004
    Posts
    4,307

    Default Re: Automatic Wupdate operation.

    Hello,

    We have converted now all nine of our products from Installshield and INNO to Setup Builder. They all work better now!
    This is music to my ears Thank you!

    A question about automatic running of Wupdate. In our programs we have added a menu option to check for updates. When the user clicks that option, we check to see if their Maintenance Subscription is current. If so, we run Wupdate and if not, we put up a screen that encourages them to renew.

    However, we also set Wupdate to run automatically every 15 days. Does automatic running also check for a current Maintenance Subscription? If not, then we will build our own 15 day checker into our programs and only run wudate silently if their subscription is current.

    Is there a way to have this be automatic?
    First of all, you should do the subscription validation from the (downloaded) web update installer package. You should not handle it from a custom wupdate.exe.

    The automatic interval checking feature requires an elevated running wupdate.exe. But it's better to use wucheck.exe (runs non-elevated) so the user does not see the elevation prompt every time the program is executed. I would suggest to build your own 15 day checker (which then calls wucheck.exe).

    Does this help?

    Friedrich

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts
  •