AE开发教程和开发实例

The ArcGIS desktop applications are COM clients. Therefore to extend the ArcGIS framework

with your own customizations, your components need to be COM compliant. Any development

environment that can adhere to the COM specification can be used: Visual Basic, Visual C++,

Delphi

predominant factor may be experience and skill level with the language. Other factors may

include performance, security and application requirements.

With ArcGIS 8.x there was one core library called esriCore.olb where the ArcObjects type

information was held. With ArcGIS 9.x, esriCore.olb has been split into smaller, more

manageable and modular libraries. Classes of similar functionality are grouped inside a

particular library. For example, geometry classes such as points, lines, polygons have been

placed inside a type library called Geometry. Map and Layer classes are located inside the

Carto library. The Library Locator utility is one of many resources that can be used to locate the

Each ArcGIS type library has an equivalent .NET interop assembly, to allow development with

the .NET API. It is important to note that these ESRI-provided assemblies are marked as

Primary Interop Assemblies (PIA). PIA indicates that an Interop assembly has been provided by

the publisher of COM types. PIAs are always strongly named; they are digitally signed to

guarantee unique identity semantics.

If the .NET Framework 1.1 is installed on the machine, all ESRI interop assemblies will be

interop assemblies inside the GAC prevents you from having to import the assemblies yourself

and also prevents the assemblies from being copied to your local directory each time they are

referenced by another project.

If you are new to .NET and COM interop and would like further information regarding ArcGIS

development using the .NET API, the ArcGIS Developer Help offers detailed documentation.

Within the ArcGIS Developer Help, go to Development Environments > .NET for a listing of

articles.