2013

DescriptionAttribute
Short description of the plug-in.Description
Localized descriptions can be specified by combining
Description with a locale code. See Supported Locale
Codes (page 103) for a full list of supported locale codes.
Icon for the plug-in; used in the installer and the Apps
section on Autodesk Exchange. The icon should be 32x32
Icon
pixels in size and support 32-bit (Truecolor) color depth.
Recommend using a BMP or ICO file format.
NOTE All path specifiers are '/' and not '\', and paths
are relative to the root .bundle folder.
Help file that explains how to use the plug-in and
provides additional information about the plug-in.
Helpfile
It is recommended to place a How To section that ex-
plains how to use the plug-in. The file can be an ASCII
text file, an HTML document, or PDF that contains all
the full documentation for the plug-in or contains a set
of redirects to where the content might be located on-
line.
Localized help files can be specified by combining Help-
file with a locale code. See Supported Locale Codes (page
103) for a full list of supported locale codes.
NOTE All path specifiers are '/' and not '\', and paths
are relative to the root .bundle folder.
Unique GUID for the plug-in. A GUID must be generated
for each unique plug-in, and is used for first run notifica-
ProductCode
tions and as the installer ID for Add/Remove Programs
in Windows when installed from the Apps tab on
Autodesk Exchange.
ProductCode should be updated if the AppVersion is
changed. This is so upgrade installs work properly and
a notification is displayed for the upgrade when loaded
into AutoCAD.
On Windows, you can use the MSI installer ProductCode
or generate a GUID using an application such as
94 | Chapter 7 Introduction to Programming Interfaces