Move custom .dlls to SharedContent folder - Intergraph Smart 3D - Administration

Intergraph Smart 3D Project Management

PPMProductFamily
3D Design and Visualization
PPMProduct
Intergraph Smart 3D
PPMCategory
Administration
SPFVersion_custom
2019 (10.0)
Version_S3D
12.1(2019)

You must save custom .dlls, including delivered .dlls that you have modified, in the [Reference Data Folder]\SharedContent\Custom Symbols folder on a central reference data server.

Use the following workflow to copy your customized .dlls.

  1. Recompile each project in a Version 2019 (12.1) client installation.

  2. Copy the new .dlls to the [Reference Data Folder]\SharedContent\Custom Symbols folder.

    • You can create hierarchy folders as needed under the Custom Symbols folder.

    • If a custom .dll has a localizer .dll, both files must be located in the same folder.

    • .dlls ending with "–Ref.dll" or "_Ref.dll" are treated as reference .dlls and are ignored. Do not copy these .dlls from the client computer containing the source code.

  3. In Project Management, run Tools > Update Custom Symbol Configuration.

    Create or update the custom symbol configuration file

  • Whenever a symbol or naming rule class is accessed, the software searches for the .dll as follows:

    1. The software checks for the ProgID entry in the xml files. If an entry exists, then the corresponding .dll is loaded, and an instance of the class is created.

    2. If an entry does not exist, the software searches previously registered .dlls on the local computer.

    3. If any entry is not found for the ProgID in either .xml file, and the .dll is also not registered on the local machine, the software returns an error. In this case, you should copy the .dll to the [Reference Data Folder]\SharedContent\Custom Symbols folder and run Update Custom Symbol Configuration in Project Management.

      If a ProgID entry exists in the .xml files, that .dll is used even though another or the same copy of the .dll is registered on the local computer. The priority order when creating an instance of an object is: CustomSymbolConfig.xml, SystemSymbolConfig.xml, and then the registry.

  • When you add a new custom .dll to the [Reference Data Folder]\SharedContent\Custom Symbols folder or modify an existing custom .dll, you must re-run Update Custom Symbol Configuration in Project Management.

  • Debugging and maintaining project references, reference .dlls, and binary compatibility are beyond the scope of this document. Contact your support representative if you have questions.