This feature seems to be really promising. This could solve the question of maintaining the same software version of applications on multiple workstations.
But I can't really work out how to use it. How exactly can I "link" a Cameyo'd application to a server or network share? Can I set up a Cameyo local server? How should I create this XML on the server?
I must be blind but I can't find the right documentation for these questions.
It is a blessing in disguise. I make Cameyo's for software, where the licence specically EXCLUDES updates. You when making a portable, I want to be able to choose whether or not automatic updates should apply.
If Cameyo updates its own software only once every few months, I think it is a waste of time if it want to check for updates at every launch.
When I start CameyoMenu or Launcher via a shortcut on the desktop. the response is much faster.
This feature seems to be really promising. This could solve the question of maintaining the same software version of applications on multiple workstations.
But I can't really work out how to use it. How exactly can I "link" a Cameyo'd application to a server or network share? Can I set up a Cameyo local server? How should I create this XML on the server?
I must be blind but I can't find the right documentation for these questions.
Perhaps the blog article was not clear enough; this feature is currently only available for the virtual app Cameyo itself. What you're seeing in the movie is just a preview.
It is a blessing in disguise. I make Cameyo's for software, where the licence specically EXCLUDES updates. You when making a portable, I want to be able to choose whether or not automatic updates should apply.
If Cameyo updates its own software only once every few months, I think it is a waste of time if it want to check for updates at every launch.
When I start CameyoMenu or Launcher via a shortcut on the desktop. the response is much faster.
First of all, don't worry about programs you make portable. They will not automatically become "auto-updatable", as this is something you would need to configure (either using an XML or Cameyo server)
Secondly, the auto-update checking is asynchronous. Meaning that neither the CameyoMenu nor the Launcher wait for it; the check is done in the background and in no way stops or slows down the virtual apps themselves. The fact that you're getting faster response from the direct shortcuts could maybe be due to the virtual engine's starting up?
Thanks for your answer. Yes, the blog said it was an upcoming feature but the feature list of the latest build included "auto-update". So I thought it was already in.
Can't wait to see it working for all the apps! Any idea when it will be ready?
It will be a part of the next major version, which includes many other changes. But there will be a Beta program which will allow you to focus on this feature.
