How to add your knowledge

Property Details

    Table of contents
    1. 1. Other Properties
    2. 2. TBP Examples

    The following table details all possible properties:

    AssemblyName Name of the .dll file, not including the path.
    Namespace The Namespace name of your .dll (as defined in the C# or VB project). Usually the same as the AssemblyName property.
    ClassName Name of the plugin class.
    MapName Name of the map interface.

     

    The default is "" (empty quotation), which means the plugin runs with the default Autodesk connection (that is, AutoCAD Map 3D or Autodesk Infrastructure Map Server 2013.)

     

    Tip

    If you want to use your own application for the map interface, specify the name for this property.

    Priority Defines the order in which the plugins are loaded.

     

    For example, a plugin class with a priority of 50 is loaded before a class with a priority of 100. The recommended value is 100. If you require a range, use values between 50 and 150.
    ExecutionTargetWeb If your plugin is designed to work in AutoCAD Map 3D Web, set this property to “true”, otherwise set this property to “false”.

     

    Note

    Plugins that use standard Windows Forms and controls cannot be used in AutoCAD Map 3D Web.

    ExecutionTargetDesktop If your plugin is designed to work in AutoCAD Map 3D Client, set this property to “true”, otherwise set this property to “false”.
    Company Name of the company that built the plugin.
    Author Name of the plugin developer.

     

    The Company and Author properties are shown in the list of plugins and also displayed if an error occurs in the application.
    DocumentKey (Obsolete - use the DMCode property instead.)

     

    Specifies the documents that cause the plugin to load. Default is "" (empty quotation), which indicates that your plugin is loaded with every AutoCAD Map 3D document. If you want the plugin to only load with a specific AutoCAD Map 3D document, set this property and add the same key to the TB_GN_DOCUMENT_KEY table.
    ApplicationKey (Obsolete - use the DMCode property instead.)

     

    Similar to the DocumentKey but is an application-wide setting. Add the application key to the TB_GN_APPLICATION_KEY table in TBSYS User.
    DeactivationKey Enables you to “switch off” a plugin or group of plugins.

     

    Use the "Options-License" property. Use the same DeactivationKey name for all plugins that belong to the same functional group.
    DMCode Data Model Code. Specifies in which modules the plugin loads. By default, the plugin loads with documents based on any kind of module. DMCodes are stored in the TB_DATAMODELCODE table. The DMCode format is “X.X.X”, where the first number represents the company, the second is the module (for example, Wastewater), and the third is the submodule (for example, Wastewater Switzerland). Modules not developed by Autodesk have a value between 3 and 99 for the company code. Company codes 1, 2, and 42 are reserved by Autodesk.

     

    For more information about the Data Model Code format, see Creating the Data Model.

     

    Other Properties

    To specify that a dialog plugin is only active with a specific form, set the Name tag in the.tbp file. In the following example, the dialog plugin MyPointClass is only visible in the form/table “MyPointName”:

    <DialogPlugIn ClassName="MyPointClass" Name="MyPointName" /> 
    
    Note

    If you set Name="" then the dialog plugin is started with all forms.

    TBP Examples

    For more information about TBP and demonstrations using sample code, see Developer Samples.