Instructions for my clients to use the auto update function

If the official documentation isn’t sufficient (link), here’s a video tutorial for another one of our products that uses the same mechanism. It should be helpful:

https://www.htmlexe.com/video/tutorial-ebook-web-update

The key point is to make sure you increase the EXE File Version Info, so the web update is triggered correctly.

gdgsupport said:

If the official documentation isn’t sufficient (link), here’s a video tutorial for another one of our products that uses the same mechanism. It should be helpful:

https://www.htmlexe.com/video/tutorial-ebook-web-update

The key point is to make sure you increase the EXE File Version Info, so the web update is triggered correctly.

Click to expand...

Thank you for your prompt and kind replay. I have make all of the entries as stated. However, how do I instruct my clients to chek for the auto update. I have increased the version number by ".1" In other words, what must they do on their end? Currently, the only way that they have to know if the version is a newer version in by donwloading the new new file then check the version number by clicking on the new fle and selecting "properties." I am missing the "automation" part of this process. What must my users do to trigger this process? Do I need to provide a special link?

What you are missing is indeed the built-in Web Update mechanism of XLS Padlock. Simply increasing the version number (for example, from 1.0 to 1.1) is necessary. Then, you can configure your application to automatically check for updates at startup or add a “Check for Updates” button to the welcome screen. When a new version is detected, users are guided through a Web Update wizard:



Users can also initiate an update via the command line switch -webupdate.