In my case, my solution would be a third-party program I already use a lot to automatically check websites for changes of content. An option which can always be changed to email or not to email when new (at least major, not RC or Beta or you could configure what level of notifications if Tihiy is inclined) versions come out. It would be at about as simple as the already implemented version check, and it could be opted out at any time for those who only want to know when they feel like it. I've always been a new version hound for all programs, OSes (beginning with ProDOS for Apple in my case), although always tempered enough to keep back-ups of at least one version behind just in case.
I wouldn't lose any sleep if Tihiy doesn't want to bother changing the current method or implementing anything new regarding it, however. I've always believed in the most gain for the least amount of work. The best bang for the buck.
Just one more option would be to give the Cfg program command line options, and implement a check box with or without options (frequency, again if Tihiy wants to make that configurable) which would create a scheduled task using said command lines to check for product updates, and would notify via a dialog if so. Again, should be fairly simple to implement, people who don't want anything running that doesn't have to can leave it unchecked (I motion that it be defaulted to not check/notify on a scheduled task). Not sure if it was this thread someone already mentioned scheduled tasks for something.
if it's too hard or unelegant to schedule/unschedule on the fly after hitting checkbox and OK, then create the task at product installation, but disable it by default. Then if the checkbox is hit and after OK, then re-enable the task. Either is just as good IMHO.
I'm done on this particular subject, I don't want to beat it to death like what happened with the activation issue.
Edit: Added info I forgot to.
This post has been edited by roirraW "edor" ehT: 21 November 2012 - 08:33 AM