Summary

Synopsis

This article discusses how the properties of the Install SpeedFolder Action affect what is written to the local ZeroG Registry file (.com.zerog.registry.xml).

Discussion

The local ZeroG Registry file, located in the same directory as the product's uninstaller, is used to maintain a record of files and actions that were installed by the product. The uninstaller uses this file to remove the files and actions at uninstall time. When the installer includes a very large number of files, this file can become large enough to cause the uninstaller to consume all of the available Heap space and produce an OutOfMemoryError.

One technique used to decrease the size of this local Registry file is to use SpeedFolders to install payload files rather than statically adding the files as Install File actions. Depending on the values specified for the properties of the Install SpeedFolder Action, either an entry will be created for each file installed by the Install SpeedFolder action or one single entry will be made for the top level directory installed by the Install SpeedFolder action. The table below shows the properties and their possible values:

As the table demonstrates, if the Install SpeedFolder Action is configured to both Install the folder and the folder's contents as well as to recursively uninstall the payload at uninstall time, the action will only create a single entry for the parent directory in the local Registry. This configuration of the Install SpeedFolder Action will allow for a much smaller local Registry file and can resolve issues where the uninstaller is consuming all of the available Heap space.

Additional Information

For additional discussion regarding SpeedFolders, please see the following HelpNet pages:

SpeedFolders