Posted by Simon Long Nov 8, 2011
Whilst testing a Thinapp today I noticed that every time I ran the Thinapp a file related to that software package was being created in the Thinapp bin directory. This isn't something that I want to happen. The file created was named the same as the ComputerName of the vm it was being excecuted on. So as you can imagine, if you have desktop estate of 10,000 desks, it could get quite missy.
With the help of Peter Bjork one of the VMware Thinapp specialists we worked out that the Entry Point that we were using to excecute the Thinapp didn't have a WorkingDirectory defined in the package.ini. This is what the entry point in the package.ini looked like:
As you can see, there is no WorkingDirectory defined. If a WorkingDirectory is not specified on an Entry Point the location of the Entry Point will be the working directory, in my case the bin directory. I edited the package.ini to read the following:
I rebuilt the Thinapp and now the application creates this application file in the application directory. Sweet.