VMware

February 26, 2009

How to Ignore Local System Files and Registry Entries Inside a ThinApp Package

Have you ever had the need for a packaged application to have access to a local folder but you don't want it to see certain files in that folder if they exist?  And what about registry entries?

Here's how to do that...


Continue reading "How to Ignore Local System Files and Registry Entries Inside a ThinApp Package"

Custom PACKAGE.INI Settings Seen or Utilized Externally to the Package

Do you ever wonder what unique configurations you can make to your ThinApp project's PACKAGE.INI which you might be abl to use or see outside the package?


Continue reading "Custom PACKAGE.INI Settings Seen or Utilized Externally to the Package"

October 07, 2008

Creating Windows Entry Points for Troubleshooting ThinApp Packages

By default, ThinApp creates Entry Points (e.g. Shortcuts) in your packaged applications for CMD.EXE, REGEDIT, and Internet Explorer. But wouldn't it be nice to have some shortcuts in your ThinApp package for troubleshooting? For example, Windows Explorer, Services, Local Machine Group Policy Editor, and other similar tools would make troubleshooting and customizing your packaged application a heck of a lot easier.

Well, here's how you do that!

Continue reading "Creating Windows Entry Points for Troubleshooting ThinApp Packages"

October 04, 2008

CachePath Setting in Package.ini

When using AppSync, remember that you now have a new entry that will allow you to control the location of the upgraded file on the local file system.

CachePath–Sets the path to the cache directory where Application Sync updates and font files are stored. This setting can contain macros like %Local AppData% which will be expanded before use. If the path is relative, it is interpreted relative to the directory where the package is stored.

The setting can be overridden at runtime by the environment variable, THINSTALL_CACHE_DIR.

If neither the CachePath setting nor the THINSTALL_CACHE_DIR environment variable are present, a default is used. The default depends on the presence of a SandboxPath setting in the package.ini file. If there is a SandboxPath setting and it is a relative path, then CachePath defaults to the same path. If there is no SandboxPath setting or the path setting is absolute, then CachePath will default to %Local AppData%\Thinstall\Cache.

For example, set the cache directory to C:\VirtCache:

  • CachePath=C:\VirtCache

With the package located in C:\VirtApps, this will set the cache to C:\VirtApps\Cache:

  • CachePath=Cache

In a typical USB key scenario, you force the sandbox to the USB key. If the packages are stored in a subdirectory, \VirtApps, on the USB key, enter the following to force the cache directory to the USB key too:

  • SandboxPath=Sandbox

About ThinApp

  • VMware ThinApp lets you deliver and deploy applications more efficiently, more securely, and more cost-effectively with agentless application virtualization.

Subscribe

Search ThinApp Blog

Lijit Search