Updates tracking


It is usually desired that users always have the latest version of the software. Messages can be used to notify only those users that run older versions of the application, providing details where updates can be obtained and what’s new.

You can also automate the process of updates by providing a link to the new version in the message, and perform the download and update automatically in the application. In this tutorial, we will focus on simply letting users know an update is available and where to get it.

It is also quite common to offers users the possibility to choose what type of updates they want. Some may prefer to only get the stable ones, whereas others want the newest features first and accept that there may be some bugs. We can solve this by grouping our updates notifications into stable and experimental channels.



Let’s suppose the user is listening on the stable branch and we want to show them the recent message if such exists. Then, we can use the code below.

var currentVersion = 1538610060;
var result = (GetMessagesResult)Message.GetMessages("token with GetMessages permission", new GetMessagesModel { Channel = "stable", Time = currentVersion } );

if(result == null || result.Result == ResultType.Error)
    // we could not check for updates
    Console.WriteLine("Sorry, we could not check for updates.");
else if (result.Messages.Count > 0)
    // there are some new messages, we pick the newest one 
    // (they are sorted in descending order)
    // No messages, so they have the latest version.
    Console.WriteLine("You have the latest version.");


The variable currentVersion is the date when you published this release (in unix timestamp format). Each time you update the application, you need to remember to update this values.

The easiest way to obtain the unix timestamp is by visiting this link or, if you are on Linux or macOS, type the following in the terminal:

$ date +%s