I am virtualising an application that relies heavily on plugins. The plugins are quite large in size and some are incompatible with eachother.
They work when there are inserted into the main folder. I have tried just pasting them into the main folder in the CHANGES folder but the app does not seem to recognize them.
Thus, i have concluded that Cameyo maintains a database of the files that it outputs into the CHANGES folder and only includes the ones it knows of into the sandbox. Is that so?
If it is, could you please specify the file/method that the files are kept track of in? I could write an app myself that scans the folder and "injects" the new files inside.
(or is there any chance this might become a feature in some upcoming update?)
1. Using Package Editor, you can add folders and files in the Files tab. 2. Use -AddFile parameter, e.g. Cameyo.exe -AddFile C:\host\file.txt %Personal%\new.txt C:\packages\appname.cameyo.exe
The above two methods modify the package with persistence.
3. Use -exec parameter to run a virtualized script that copies plugins (and registers if necessary), e.g. C:\packages\appname.cameyo.exe -exec C:\scripts\copy.vbs
Affects only the package's sandbox, i.e. does not modify package itself
I have found a much more elegant way to do this. I will tell it for anyone who stumbles upon this topic and has the same question.
I have included a file explorer inside the package, with a different entry point (shortcut). If you want to add files to the sandbox (a mod or a plugin etc) you just have to copy/paste them into the third-party file explorer, in the "location" you would have natively.
They are added to the sandbox and the virtualisation engine keeps track of them. It works perfectly for me.
I used Explorer++ myself though i don't think it's FOSS. I guess you can use anything. It also enables you to copy out the program files without using cameyo.exe.
