ArcGIS Engine Developer Guide

APPLICATION DEVELOPMENT AND LICENSE INITIALIZATION
For a detailed description on how to use the
LicenseControl, see Chapter 3, ‘Developing with
ArcGIS controls’, and Chapter 6, ‘Developer
scenarios’.
IAoInitialize
Application AoInitialize
The coclass AoInitialize and the IAoInitialize
and ILicenseInformation interfaces it implements
are designed to give support to a
developer for license initialization.
In this example, even though ArcInfo would also
provide the functionality required, the developer
has opted not to initialize with an ArcInfo
license. It would be unnecessary to consume an
ArcInfo license for this simple application.
Step 1: Check product license
availability
Step 2: Check extension license
availability
LICENSE CONFIGURATION
There are two ways to configure a custom application with a license: using the
LicenseControl and programmatically.
Use the LicenseControl to automatically perform license initialization within
simple graphical user interface applications using the MapControl,
PageLayoutControl, TOCControl, ToolbarControl, ReaderControl, SceneControl,
or GlobeControl in the COM and .NET APIs. If greater control is required over
license initialization, particularly when checking extension licenses in and out (the
LicenseControl will check out extension licenses for the duration of an
application’s life), consider programmatically performing license initialization.
To programmatically perform license initialization use the AoInitialize object and
the IAoInitialize and ILicenseInformation interfaces it implements. The ESRI License
Initializer Visual Basic 6 and Visual Studio .NET add-ins can be used to
automatically generate and add license initialization code to a custom application.
See Appendix B, ‘ArcGIS developer resources’, for further information about the
add-ins or the licensing samples found in
\DeveloperKit\Samples\Licensing_and_Extension_Checking.
EXAMPLE A—MINIMUM LICENSE IS ARCGIS ENGINE WITH 3D AND
SPATIAL EXTENSIONS
In this example, the application requires at minimum an ArcGIS Engine license.
In addition, this developer has decided that if an ArcGIS Engine license is not
available, the application could run with an ArcView or ArcEditor license instead.
The application also requires 3D and spatial extension functionality for it
to run successfully, so both of these extensions need to be checked out for the
duration of the application.
In this case, the application will first attempt to initialize against the ArcGIS
Engine product license. If that fails, it will attempt to initialize against an
ArcView license, and if still unsuccessful, the application will finally attempt to
initialize against the ArcEditor product license. The following sections outline the
steps that must be taken to initialize the application with a license.
Attempting initialization with the ArcGIS Engine product license
As noted above, to run successfully the application requires at minimum an
ArcGIS Engine product license along with the corresponding 3D and Spatial
extension licenses. The application’s first attempt at initialization should be
against this minimal level of product licensing. The application’s attempts at
initialization follow the process discussed earlier.
1. Check whether an ArcGIS Engine product license is available. If yes, proceed
to the next step in the initialization process. If not, discontinue this attempt
and restart initialization with any secondary level of allowable product licensing.
2. Determine whether a 3D extension license is available for the ArcGIS Engine
product license.
Chapter 5 • Licensing and deployment • 265