Best option for upgrading Servoy Offline?

When running Servoy in Offline mode (designer.enabled=false in the servoy.properties file) the client won’t automatically check for version updates. This is a good thing. However, how best to manage the version updates for the end user? In my solution, I’ve removed the menus (I don’t like giving access to things like “delete all records”, or even showing those menus with the items disabled as it creates clutter.)
Consequently, the Help menu doesn’t appear to the end users either. Short of doing a full install over the end user’s existing installation, is there a minimum set of files the developer can distribute to upgrade the end user? or is that too hard eg the list of files changes with each upgrade. Any other approaches to this?

A thought - could there be a function application.checkForUpdates()
In this way, we could control this through a method, without giving access to the menus.

Thanks in advance for any feedback.

for the offline version you have to make a new installer based on the latest version (which users can run ontop of current install)

Thanks for the response Jan.

Do you think my suggestion (a function that runs the update from a method) could be added to the wishlist?

It seems a bit strange req. at this point in time, we might update something in a new install which could brake your special install, I whould expect you want to make sure your installs don’t break by our autoupdate.

I see your point, but what I wanted was a way to update each Servoy Offline installation from a server, to avoid having to make a new installer for each upgrade. This would only run at a time that I specify, once I’ve checked that my solution runs ok on the new release. It seems a pity not to use the functionality of Servoys autoupdate, if we can get the timing right.