Build Settings

Overview Output Upload Constants Code SigningResourcesPre/Post Build

Note: Changing any of the setting below after the initial release of the client executable will cause the distributed client executable to update itself when run.

Custom Icon

Note: This feature requires the update to be built on Windows 2000 or greater.

Use custom icon

If checked, you can use a custom icon for the client update executable.

Path to local icon file:

The full path and filename of the icon file (.ico) to use for the client update executable. You can click the Browse button to select an icon file.

Custom Resource Information

Note: This feature requires the update to be built on Windows 2000 or greater.

Note: TrueUpdate reserves the 'Private Build' resource field for important program information. You should never modify this resource information manually.

Stamp executable with custom information

If checked, you can stamp the client update executable with your own custom information.

Product version:

The product version. For example, "1.0.0.19". If you leave out any digits they will be replaced with zeros.

Product name:

The name of the product. For example, "My Nifty Application."

Company name:

Your company name. For example, "Indigo Rose Software."

File description:

A short description about the purpose of the published executable. For example, "My Nifty Application runtime."

Internal name:

The internal name of the product. Usually the same as the Product name.

Trademarks:

Trademark notices for the product.

Copyright:

Special build:

Any 'special build' notes that may apply.

Tip: In order for the TrueUpdate client to function correctly, a section of its resources must be modified when publishing. If you are trying to publish on an unsupported operating system below Windows 2000, or are having problems, you can set a hidden preference that will allow a build to complete with warnings, instead of fatal errors when updating its resources. Open your TrueUpdate preferences file (see the Folders preference for its current location) in a text editor and locate the XML tag "SupressResourceStampError". Then change its value from 0 to 1. While this allows you to publish, skipping this crucial step means that the client will always require updating itself when it is run.