You’ve all been quite clear about requesting an AutoUpdate feature for Cameyo’d apps. You asked for simplicity, which is something we value a lot at Cameyo.
This feature has been developed & ready, but for now it is only available for one specific virtual application: Cameyo itself!
The latest Cameyo build (2.0.873) contains a new AutoUpdate feature, which has been generically designed for ANY Cameyo virtual application. We’ve been able to beta testing it (by providing a 2.0.872 earlier build to our beta testers), and it seems to do the job. So here’s a preview of what will be soon made available for any Cameyo’d app:
Noticed that updates can be deployed while the virtual app is in use?
Also, if you own an iPhone / iPad, you might find it similar to their app updating functionality. That’s how simple we believe updating should be.
How it works:
On the virtual app side, the autoupdate path can be either linked to a Cameyo server or to any path containing the package’s XML file (network share or http(s)).
If linked to a Cameyo server, then all the configuration is done for you and you don’t need to worry about a thing.
If you link the virtual app to your own autoupdate path (i.e a network share with up-to-date apps), then the package just needs to know where to find an XML for that latest version. This is indicated in the app’s “AutoUpdate”. For example, an XML path may be:
On the server, the XMLfile has to indicate the latest app’s version and the update mode:
And in the same directory, the EXE file has to be present with the same name (ending with .EXE instead of .XML), so there need to be two files:
That’s it. Easy to configure, easy to use.
There’s a lot of extended conditions, modes, exceptions that can be customized into the XML, but that’s not the aim of this post.