Shared assemblies
|
Deployment notes
|
The System assembly is the lowest level library in the ArcGIS architecture. The assembly contains components that expose services used by the other libraries composing ArcGIS. | |
The SystemUI assembly mainly defined types used by user interface components in the ArcGIS system. Interfaces such as ICommand and ITool are defined in this assembly. Implementation of these types is normally done in one or more libraries, higher in the architecture. | |
The ADF assembly provides the .NET base classes, component category unique IDs (CATIDs), and utility classes that were previously delivered in the Utility assembly that has been deprecated for the 9.2 release.
|
|
The Utility assembly has been deprecated from 9.2 forward. Most of the functionality that previously existed here has been moved into the new ADF assembly.
|
You can still deploy applications that use the Utility classes and any projects referencing them will continue to operate as normal; however, be aware that the Utility classes are now deprecated and may be removed entirely in a future release.
|
The Geometry assembly contains the core geometry objects, such as Point, Polygon, Polyline, etc. along with Geometry types and definitions. The Geometry assembly also defines and implements the spatial reference objects for both projected and geographic coordinate systems. | |
The Display assembly contains the components that support drawing symbology to an output device. Screen displays, symbols, colors and feedback objects, along with their supporting objects are all defined in the assembly. | |
The Server assembly contains the objects used to obtain a connection to the ArcGIS Server. The connection is managed via the objects in this library, but objects from other libraries can be created by using functions on the server object. | |
The Output assembly contains the objects required generate output, most commonly from Maps or PageLayouts, to both printers and plotters or exporting to files. | |
The GeoDatabase assembly contains types for all the definitions relating to data access. Features, tables, networks, TINs are all defined in the GeoDatabase assembly. The implementation of many of the types is contained in the respective DataSource assembly. | The usage of some objects in this library requires the Geodatabase Update extension for ArcGIS Engine Runtime. |
The GISClient assembly contains objects for working with remote GIS Services. These services can be provided by either ArcIMS or the ArcGIS Server. | |
The ArcWeb assembly enables connections to ArcWeb services. | |
The DataSourcesFile assembly contains the workspace factories and workspaces for vector data formats supported by the GeoDatabase API. | |
The DataSourcesGDB assembly contains the workspace factories and workspaces for vector and raster data formats supported by the GeoDatabase that are stored within an RDBMS. | |
The DataSourcesOleDB assembly provides workspaces for working with OleDB based data sources. | |
The DataSourcesRaster assembly contains the workspace factories and workspaces for file based raster data formats. | |
The DataSourcesNetCDF assembly contains objects used for accessing netCDF files and for creating rasters, features, or tables from netCDF variables in ArcGIS. | |
The GeoDatabaseDistributed assembly contains the objects required to perform, checkout / checkin to support distributed GeoDatabase. | |
The GeoDatabaseExtensions assembly contains objects to aid in the creation, management, and use of terrain datasets and cadastral fabrics.
Note: At the 9.2 release, the cadastral fabrics related objects are not yet fully implemented and we recommend that developers do not utilize them until the Cadastral Analyst extension is released.
|
|
The Carto assembly contains the objects for displaying data. The PageLayout and Map objects are in this library along map layers, renders for all the supported data types. This assembly also contains the MxdServer and MapServer objects used by servers to display map data in a client server environment. | |
The NetworkAnalysis assembly supports the creation and analysis of utility networks. | |
The Location assembly contains objects related to working with location data. This can either be route events or geocoding locations. | |
The GeoAnalyst assembly contains core spatial analysis operations that are used by both the SpatialAnalyst and 3DAnalyst extensions. | Requires a 3D or Spatial extension for ArcGIS Engine Runtime. |
The Animation assembly contains objects to work with animations in Map, Scene and Globe. In ArcGIS 9.2, with ArcGIS Desktop, the animation functionality is available in the ArcMap, ArcScene, and ArcGlobe applications. However, when working with ArcGIS Engine, animation functionality is not available for the Map control. It is only available for the Scene and Globe controls, which are supported with the 3D Analyst extension. | |
The Maplex assembly contains the objects for labeling features using the Maplex Extension. Other Maplex objects can be found in the Carto assembly. | Requires a Maplex extension for ArcGIS Engine Runtime. |
The Geoprocessing assembly implements the Geoprocessing framework in addition to the base set of Geoprocessing tools. The tools available depend on the licenses available to you. See the individual tools for specific license information. | Some geoprocessing tools and functionality require an extension license. See the documentation for each tool for specifics. |
The NetworkAnalyst assembly provides objects for working with network datasets. These objects allow you to perform network analysis in your applications. | Requires a Network Analyst extension for ArcGIS Engine Runtime. |
The Schematic assembly implements the non user-interface functionality of the Schematics extension. It handles the core objects of the ArcGIS Schematics extension, used to manage schematic data and processes. The Schematics extension supports the analysis, display, and manipulation of schematic data within ArcGIS. | Requires a Schematic extension for ArcGIS Engine Runtime. |
The SpatialAnalyst assembly contains objects for performing spatial analyst on raster and vector data. | Requires a Spatial extension for ArcGIS Engine Runtime. |
The 3DAnalyst assembly contains objects for performing 3D analysis of data, along with the support for displaying 3D data. | Requires a 3D extension for ArcGIS Engine Runtime. |
The GlobeCore assembly contains objects for performing analysis of globe data, along with the support for displaying globe data. A control is available in this assembly for developers to use. | Requires a 3D extension for ArcGIS Engine Runtime. |
The Controls assembly contains controls for application development including commands and tools for use with the controls. | Applications that utilize the GlobeControl or SceneControl require a 3D extension for ArcGIS Engine Runtime. |
The TrackingAnalyst assembly implements the non-user interface functionality of the Tracking Analyst extension to ArcMap. The Tracking Analyst extension supports the display, analysis, and manipulation of temporal data within ArcGIS. |