ThinApp Scripts and Killing Lingering Processes
ThinApps occasionally require some special manipulations to get working correctly. One of the most common issues that I’ve seen with otherwise working ThinApp packages is a failure to close correctly. Sometimes, even after a ThinApp is closed, a process will be left running that might keep the sandbox undesirably locked or cause issues with re-execution. An easy way to resolve that issue is with a ThinApp Script. These scripts can be used to solve all sorts of issues. A ThinApp Script is just a VBS script that runs at one of four specified points in a ThinApp’s execution. The vbs script can be named anything, but should be placed as a sibling with the package.ini file (you only get one vbs file though a script can call another script ad infinitum), in the root of the package. The vbs script will be automatically baked into the package, and each of 4 optional functions will be executed at the appropriate time. Those functions are as follows...