About custom component deployment
Custom components are typically dynamic link libraries (.dll files) that extend the functionality of an existing host application (an executable). Double-clicking a .dll file does not accomplish anything (verses double-clicking an executable, which starts the application); it must be consumed by the host application. The host application for ArcGIS-based custom components is an ArcGIS for Desktop application (ArcMap, ArcCatalog, ArcGlobe, or ArcScene).
The following are necessary for custom component (.dll) deployment:
- Prerequisite—Ensure that the computer for which the custom component will be used has the appropriate ArcGIS for Desktop application installed and that it's licensed.
- Install the .dll file and any ancillary files (Help files, datasets, and so on) on the same computer.
- For ArcGIS custom components based on implementing Component Object Model (COM) interfaces and Esri base classes, use the ESRIRegAsm utility to register the .dll file.
See How to deploy a custom component using a setup project for a custom component deployment example.
See Also:How to deploy a custom component using a setup project
How to ensure that COM component category and COM interop are used in custom components
Obtaining the Category and Caption property information of a custom component
|Development licensing||Deployment licensing|
|ArcGIS for Desktop Basic||ArcGIS for Desktop Basic|
|ArcGIS for Desktop Standard||ArcGIS for Desktop Standard|
|ArcGIS for Desktop Advanced||ArcGIS for Desktop Advanced|
|Engine Developer Kit||Engine|