Extending ArcObjects  

About Class Extensions

This topic is relevant for the following:
Product(s): ArcGIS Desktop: All
Version(s): 9.0, 9.1, 9.2, 9.3
Language(s): VB6, VC++
Experience level(s): Intermediate to advanced



Class extensions are the simplest and most important way of customizing geodatabase behavior. In particular, they provide the following capabilities:

Class extensions are at their best when used for important business rules that can be simply implemented without serious performance considerations.

These capabilities could often instead be provided in application code; for example the handling of edit events could be implemented as an editor extension for the ArcMap application. There are many advantages and disadvantages of class extensions relative to application customization. These are summarized in the following table.

  Class extensions Application customization
Advantages

Database customization is always available. It is not dependent on a particular application such as ArcMap being present. This can be important for feature classes accessed from ArcGIS Engine or ArcGIS Server.

Business logic is stored closely to the data.
A level of encapsulation is guaranteed.

Easy to implement and tightly integrated with the application user interface.

If customization fails then user can access important data with other tools.

The DLL is only required by those users who need the specific customization functionality.

Disadvantages

All ArcGIS users require access to the customization DLL, even to view the data.

If the customization fails at runtime, the data cannot be accessed from ArcGIS (this can also be considered an advantage that ensures data integrity).

The developer cannot make any assumptions that a particular application will be running. This can limit functionality.

An object class can only have one class extension.

You cannot easily extend annotation feature classes or dimension feature classes.

There is a possibility that users could avoid business rules by running the application without the customization.

Implementation is sometimes duplicated among several applications.

The customization is only available when the application is running.


Back to top

See Also Pipe Validation Class Extension Example, Managing Class Extensions, Timestamper Class Extension Example, Class Extensions and Relationship Classes, and Class Extensions for Annotation and Dimensions.