About limitations on using ArcGIS Engine controls in WPF
ArcGIS Engine controls are Windows Forms controls. Before developing a Windows Presentation Foundation (WPF) application using ArcGIS Engine controls, consider the following limitations:
- The ArcGIS License Control cannot be used when hosted in a WPF window. You must initialize the ArcGIS Engine license programmatically. For more information, see Licensing ArcGIS Engine controls in WPF.
- The properties and events of ArcGIS Engine controls are not accessible through Extensible Application Markup Language (XAML). You must programmatically access them in the code behind file.
- ArcGIS Engine controls do not have dependency properties, and only one-way data binding is supported. ArcGIS Engine control properties can only be bound to a WPF element, and the opposite binding is not supported.
- ArcGIS Engine controls are rendered separately from WPF elements. As a result, all display related properties of a WPF host container, such as Transform, Clip, and Opacity, have no effect on the control.
- Windows Forms controls draw outside of the WPF drawing framework and are assigned the highest rendering order. Therefore, you should avoid the following:
- Overlapping WPF elements on top of the ArcGIS Engine controls
- Overlapping ArcGIS Engine controls on WPF elements
These limitations apply to all Windows Forms controls that are hosted by a WPF application.
See Also:
WPF Interoperation: "Airspace" and Window Regions OverviewWPF and Win32 Interoperation Overview
How to host an ArcGIS Engine MapControl in a WPF application
Using ArcGIS Engine Controls in WPF
| Development licensing | Deployment licensing |
|---|---|
| Engine Developer Kit | Engine Runtime |
| ArcInfo | |
| ArcEditor | |
| ArcView |