This has to be a common problem, but the discussion topics are not quite the same scenarios. I must be using the wrong search terms to search by in the forums.
First, the issue in simple terms.. and then greater detail: I'm having an issue where a very simple app is created, but if the app is re-built with only a couple of changes, not all files in the "existing" users's Sandbox will be updated to reflect the change. Meaning, if I maintain the same Sandbox path, and it is reused on the updated app, the sandbox will sometimes continue to use the old files from the prior build.
Example: Let's say the package consists of...
ThinApp_Package.exe (living in \\networkshare\AppHome)
App.exe (original)
xxx.dll
yyy.dll
user_settings.ini
another_config.ini (original)
SandboxPath=D:\SandboxFolder\
SandboxName=App-Saved-Files (Sandbox shows the original files above just fine)
Now, if our developer creates a new "app.exe" and it uses a new statement to Read/Write in the "config.ini", I will recompile the app with those two files updated.
Rebuilt_and_Updated_ThinApp_Package.exe (living in \\networkshare\AppHome)
App.exe (updated)
xxx.dll
yyy.dll
user_settings.ini
another_config.ini (updated)
SandboxPath=D:\SandboxFolder\
SandboxName=App-Saved-Files
(The updated "App.exe" runs fine and as expected, but continues to refer to the original "another_config.ini" in the Sandbox from the prior build and does not update... so I have no choice but to delete the Sandbox and lose the users settings)
More details: If this is not a common, simple issue (which, I'm sure it is, and I'm overlooking something... I'm not too skilled with ThinApp).
We have several, similar programs of that hosted in the same manner.. and have for years. But, it appears that this one is giving me a hassle and I cannot pinpoint the change that causes this behavior.
So, I guess a general question is, "What is the decision process within ThinApp that would direct the application to view Sandbox Content over -internal- compiled content if the internal content is newer or different size?" The only common thing between the compiled content and sandbox content is the file name.
Thanks for helping an amateur.
<bump> No ideas?
Hi,
What is the isolation mode of the folder that contains the 'config.ini' file?. By default, you will not see this file visible in the sandbox.
If you are using WriteCopy isolation, then any update to this file will be written into the sandbox.
Hey there, thanks for the reply. The project's Default isolation is "WriteCopy". But the folder that contains the config.ini file is "Full". (stated in the original post). You can view the INI the sandbox just fine, as expected... except now it is not updating with the one in the package. There was never an answer, so I had no choice but to delete the Sandboxes... it is fine now. But it would be nice to know how/why ThinApp will suddenly misbehave and not update the file. Reading some undertones in other posts, it seems to happen now and then.
Thanks again.
