Cameyo

olliebean · Newbie

Upgrading packages to the beta engine

olliebean · Newbie

I'm doing exactly that, opening in Package Editor 2.5 and allowing it to update the package. What seems to be happening is that the folder layout in the data folder has changed from 2.0 to 2.5 (e.g. %AppData% and %ProgramFiles% are now in a folder called PROG which didn't exist in 2.0), and when I run the package it doesn't recognise the data from the 2.0 package and starts from scratch.

If it matters, I was previously using 2.0.807.0, which isn't the most recent release version. I'm also storing the data directory under the executable's directory, rather than in the default location. Do either of those make a difference?

-- Edited by olliebean on Friday 30th of August 2013 01:40:28 PM

mule · Guru

Hello Olliebean,

How are you upgrading the packages? When I open a 2.0 package in Package Editor 2.5, the conversion is done automatically and Data storage is retained from the 2.0 package.

mule · Guru

Here's something to try as a workaround:

1. Run your 2.0.807 package with -repackage parameter (documentation here)

2. Copy .\%AppID%.cameyo.data\VOS folder to have as a backup to a different location in case you need it later, i.e. NOT in the same folder or sub-folder hierarchy as .\%AppID%.cameyo.data

3. I then ran my 2.5 package with -remove parameter; this will delete the sandboxes of both 2.5 and 2.0.807 packages, so be sure your backup copy of the VOS folder is in a different location. If it's in the sandbox, e.g. next to the original VOS folder, it will be deleted, too! You can skip or delay this step if paranoid.

4. Open 2.0.807 new package, e.g. appname.cameyo.old.new.exe, in Package Editor 2.5 and allow conversion to take place

5. Launch new converted 2.5 package, e.g appname.cameyo.old.new.exe, to see if customized settings are retained