18.04.2015 Views

ArcGIS Engine Developer Guide

ArcGIS Engine Developer Guide

ArcGIS Engine Developer Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

WORKING WITH THE ARCGIS CONTROLS<br />

property pages at design time, programmatically, or at runtime by the end user if<br />

the ToolbarControl is in customize mode.<br />

You can also extend the suite of commands provided by <strong>ArcGIS</strong> <strong>Engine</strong> by<br />

creating their own custom commands, tools, and menus to work with the <strong>ArcGIS</strong><br />

controls. The HookHelper, GlobeHookHelper, and SceneHookHelper objects can be<br />

used to simplify this development. Refer to the ‘Building applications’ scenarios<br />

in Chapter 6, ‘<strong>Developer</strong> scenarios’, to see how to build a custom command using<br />

the HookHelper object.<br />

The LicenseControl is only available with the<br />

COM (ActiveX Control) and .NET (Windows<br />

Control) APIs.<br />

Refer to Chapter 5 ‘Licensing and deployment’<br />

for more details about the concepts of licensing.<br />

LICENSECONTROL<br />

The LicenseControl is used to initialize an application with a suitable license(s)<br />

for it to run successfully on any machine it is deployed on to. The LicenseControl<br />

will configure the licenses at application start time when the form or dialog box<br />

containing the LicenseControl is loaded. Use the LicenseControl to automatically<br />

perform license initialization within simple graphical user interface applications<br />

using the MapControl, PageLayoutControl, TOCControl, ToolbarControl,<br />

ReaderControl, SceneControl, or GlobeControl. If greater control is required<br />

over license initialization, particularly when checking out and in extension licenses<br />

(the LicenseControl will check out extension licenses for the duration of<br />

an application’s life), use the AoInitialize object in the System library to programmatically<br />

perform license initialization.<br />

The LicenseControl is visible within a visual design environment but is invisible<br />

at runtime, so unlike the other controls the LicenseControl does not provide any<br />

user interface in an application. In design time the LicenseControl property pages<br />

must be used to configure the application with product and extension licenses.<br />

Products<br />

Select at least one product license with which the application can be initialized.<br />

By default, the LicenseControl will try to initialize the application with the<br />

<strong>ArcGIS</strong> <strong>Engine</strong> product license. If the product you require is not licensed, you<br />

may optionally initialize the application with a higher product license. For example,<br />

if you select the <strong>ArcGIS</strong> <strong>Engine</strong> license and the ArcView license, the<br />

48 • <strong>ArcGIS</strong> <strong>Engine</strong> <strong>Developer</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!