I have a reliably reproducible issue here. I add files to a package by using Package Editor UI. I have a directory named 'lib' with a few jars (6) and 2 text files with no extension (named NOTICE and LICENSE). I import the 'lib' dir using the PackageEditor.exe toolbar button. The files all show up in the UI, I save the package, all good so far.
When I execute the package, I check the %APPDATA%\VOS\AppID\... structure for the files NOTICE and LICENSE in the 'lib' dir and they are not there.
There are other directories as well that I add and they do not show up in the VOS direcotry hierarchy. I don't know what I have done wrong here. It seems random the files and dirs that do not show up.
I do not know how to proceed.
Any knowledge/assistance is appreciated.
The exported package properties from PackageEditor here:
I'm currently having the same issues across multiple versions (2.5.1137.0, 2.7.1291.0, and 3.0.1390).
I execute the package, but as joebalt said, when I navigate to the directory %APPDATA%\VOS\AppID\ I only see a fraction of the files that are in the package (and sometimes no files at all).
I will note that I have some existing packages that I build daily from xml that I produce and pass to Cameyo.exe using the -BuildPkg parameter, and those builds are unaffected by this issue.
I only run into this when I build the package using the package editor UI.
Whether a file is deployed or not on the disk in the VOS directory does not mean the file was not added to the virtual package. A Cameyo package only extracts files when needed: when they're READ by the *virtualized program* (in DISK virtualization mode) and/or when WRITTEN into (in DISK and RAM virtualization modes).
To verify whether that's your case, you can try either of these:
a- Run your .cameyo.exe package with -ExtractAll parameter, and then absolutely everything will be deployed on disk.
or:
b- Run your .cameyo.exe package with "-exec cmd.exe" parameter (or any virtual module that can list a directory's contents) and try to access said directory from it, and you'll see that it's seen by the program, despite not being deployed on disk. Here's a screenshot illustrating this:
Once you understand this and confirm that this is your case, is there a way to change this behavior? Yes, if you prefer. Through the Package Editor's Properties menu when right-clicking on the relevant files:
I think what trentj and I are trying to understand is why is there a difference between the package when built in the Package Editor UI vs. from the command line (-BuildPkg option). I have observed the different behavior between the 2 packages (one created in the UI, the other via cmd line). The one created via the cmd line deploys all the files (I have verified the counts in Windows Explorer, properties dialog), but the package from the UI does not.
The behaviors here are different depending upon how the package was created - that is our confusion.
