Deploying in-process components (DLLs)
|
About deploying in-process components
All ArcGIS .NET customizations require the following three items to be present on target machines:
- The correct version of the .NET Framework. For detailed information on supported .NET Framework versions, see System requirements.
- The appropriate ArcGIS installation. This provides the ESRI primary interop assemblies, which the setup program installs in the global assembly cache (GAC). For example, deploying a stand-alone geographic information system (GIS) application that only requires an ArcGIS Engine license, necessitates an ArcGIS Engine Runtime installation on target machines.
- The executable code and resources for your .NET customization.
If .NET Framework 2.0 is found on the machine when the installation runs, the .NET Support feature is enabled during the typical installation. .NET support is a separate option in the ArcGIS installation; this needs to be selected during installation on both the development and target machines for .NET customizations to succeed. If you did not install .NET support originally, you can run the installation program again and choose the Modify option to add features to your ArcGIS installation.
If your customization is a component that extends the ArcGIS framework in Component Object Model (COM) applications (for example, a custom ArcGIS Engine application or the ArcGIS Desktop applications), deployment may be more complex than that of stand-alone applications, because such components must be registered with COM. For more information, see
How to register .NET components with COM and refer to COM interop topics on the Microsoft Developer Network (MSDN) Web site.
Remember that the ESRI ArcGIS primary interop assemblies and .NET Framework should already be installed on the target machine.
See Also:
Deploying EXEsCreating a custom install program
