ArcGIS Engine Developer Guide

APPLICATION DEVELOPMENT AND LICENSE INITIALIZATION
As noted in the previous section, using an
ArcView license with an ArcGIS Engine application
will give you access to all the functionality
available to a standard ArcGIS Engine license.
Likewise, using an ArcEditor license with an
ArcGIS Engine application that performs
multiuser geodatabase editing will give you
access to all the functionality available to an
ArcGIS Engine license with the Geodatabase
Update extension.
Applications built with any of the ArcGIS controls
must also adhere to this license initialization
process. MapControl, PageLayoutControl,
ReaderControl, TOCControl, and ToolbarControl
applications require the ArcGIS Engine Runtime,
ArcView, ArcEditor, or ArcInfo product licenses.
Since GlobeControl and SceneControl extend
core ArcGIS Engine functionality, they require a
corresponding 3D extension license in addition
to the core product license.
different from the Desktop Concurrent Use licensing, they actually utilize the
same technology. This means that there is no mechanism for you, as an ArcGIS
Engine developer, to differentiate between a Single Use and a Desktop Concurrent
license, and hence, you would treat them the same.
Once an application has been initialized with a license, it cannot be reinitialized;
an application is initialized with a license for the duration of its life. For example,
you can’t write an application that starts up with an ArcView license and
later switches to ArcEditor.
When initializing an application with a license, the following must be considered:
• The types of product licenses with which the application can run. For example,
an enterprise geodatabase editing application will not be able to run
with an ArcGIS Engine license or an ArcView license. However, it will be
able to run with an ArcGIS Engine with a Geodatabase Update extension
license, an ArcEditor license, or an ArcInfo license.
• The types of product licenses available to the application. For example, an
application that can be run with an ArcGIS Engine license will also run with
an ArcView, ArcEditor, and ArcInfo license. However, you may not want to
consume an ArcInfo license with such an application.
When an application is initialized with a particular product license, a connection
is made to a license server. All subsequent calls to check extensions out and in are
made to the same license server. As such, you cannot use a combination of licenses
from different license servers or Engine Single Use.
• If an application is initialized with a Desktop Concurrent license, the application
will subsequently only be able to access that Desktop Concurrent license
server and its extension licenses.
• If an application is initialized with a Desktop Single Use license, the application
will subsequently only be able to access that single-use license server and
its extension licenses.
• If an application is initialized with the Engine Single Use license on your
machine, the application will subsequently only be able to access the Engine
Single Use extension licenses.
It is possible before initialization has been performed to query the license servers
(Desktop Concurrent or Single Use) and Engine Single Use to see if the licenses
you require are available. If all the licenses you require are available using Engine
Single Use, then it is recommended you use it instead of the Desktop Concurrent
and Desktop Single Use licenses. This means you will not limit the Desktop
Concurrent licenses available to any other users.
THE INITIALIZATION PROCESS
The initialization of an application with a license must be performed in the
following order:
1. Check whether the product license is available.
2. Check whether extension licenses are available (if required).
3. Initialize the application with the product license.
262 • ArcGIS Engine Developer Guide