[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Collapse]WPF Controls
  Prerequisites
 [Expand]What's Installed
 [Collapse]Common Concepts
  [Expand]Themes
  [Expand]Images
  [Expand]Printing and Exporting
  [Expand]Saving and Restoring Layouts
   Typed Styles
  [Expand]Touch Support
  [Expand]Expressions
  [Expand]Formatting Values
   Prism Adapters
  [Expand]Data Sources
   XAML Namespaces
 [Expand]MVVM Framework
 [Expand]Controls and Libraries
 [Expand]Scaffolding Wizard
 [Expand]Localization
  Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Reporting
[Expand]Report and Dashboard Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]CodeRush
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Prism Adapters

The DevExpress.Xpf.PrismAdapters.v18.1 assembly provides Prism 5 and Prism 6 adapters for the following controls:

The adapter instances are retrieved via the static AdapterFactory.Make method.

The code snippets below illustrate how to register the DevExpress Prism adapters in a Prism Unity bootstrapper.

Prism 5/6

Prism 6

Due to the Prism's limitation in handling adapters for FrameworkContentElement descendants (specifically NavBarGroup and NavigationFrame), region names need to be specified in XAML using the DXRegionManager class. See the following code snippet:

The DXRegionManager attempts to obtain the currently used version of Prism based on the registered adapters and loaded assemblies if the value of the DXRegionManager.PrismVersion static property is not specified. It is recommended to set this property to the appropriate value manually.

Expanded Examples

Is this topic helpful?​​​​​​​