How to use VersionAvailableEventArgs

4 posts, 0 answers
  1. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 11 Oct 2011 Link to this post

    Hi S?ren, Yes, I will write something when I am finished. My biggest issue is lack of documentation. For example, now I am trying to get LastVersionAvailableEventArgs working. Should I do like this: if (Analytics.LastVersionAvailableEventArgs.CurrentVersionDeprecated) { DialogResult result = MessageBox.Show("There is an update available!", "New version", MessageBoxButtons.OKCancel); Why do I have to depriate a release? It would be nice to understand your thinking a little? BR, Mattias
  2. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 11 Oct 2011 Link to this post

    Hi Mattias I'm sorry that the documentation (or lack thereof) leaves you wondering so much. I'll bring this to the attention of some of the decision makers. With regards to your question: No, the CurrentVersionDeprecated is a flag that is returned if the version of the application that is report to our server has been tagged as deprecated. One use case for this could be that a specific version contains bugs that you do not want to have users continue running on. Tagging the release as deprecated on our servers will allow you to react to the mentioned flag in your application (show a polite 'update required' notice and perhaps initiate a download of the latest version). There is no requirement to deprecate a release, it is merely a tool for you to use. The NewVersionAvailable event is only raised if a public release with a higher version has been configured on our servers. This also means that you will not receive the event if no higher versions have been defined, regardless of whether you tag a specific version as deprecated. So in that sense you need to somewhat buy into defining your versions on our servers so we know what to send back. Hope this helps (and again, sorry for lack of clear documentation on this) Best regards Soren EQATEC Team
  3. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 11 Oct 2011 Link to this post

    Thank you for the answer. That there is no event unless there is no new version makes it impossible to say that "Your version is up-to-date" with 100% accuracy. There are several reason the check might fail, for example firewall which prevents the the program to talk to EQATEC. Suggestion: The event should always be raised with the information and say latest version or similar. Then I know that if no event, I can say "I don't know, please go to the url .... and check." BR, Mattias
  4. Guest
    Guest avatar
    506 posts
    Member since:
    Feb 2012

    Posted 11 Oct 2011 Link to this post

    Hi Mattias The VersionAvailable event was conceived as a convinient way of notifying users of potential updates to their software and not as a "safe" check for updates. Hence the raise to make it an event that could be raised some time after Start is called and not as a method call to invoke. This was a least some of the original reasoning behind the design but you are right to question the validity of these assumptions. You could question the fact that the event may not be delivered with 100% accuracy (firewalls etc. as you mention) and you could question the behavior of not raising an event if the version is the newest one available. You could even question whether or not the event should be raised if the server could not be contacted (though we do allow the application to override the automatic synchronization to the server which would sort of invalidate such an effort). All in all, I definitely see your point and I'll forward your suggestion along with some of the potential incorrect design assumptions to our request backlog. Best regards Soren EQATEC Team
Back to Top