Devolutions.AvaloniaTheme.DevExpress 2026.8.27

Custom Avalonia Themes developed by Devolutions

DevExpress Theme [Work in Progress]

This theme is currently based on Avalonia.Themes.Fluent, both as a fallback for any controls not covered yet and as starting point for our (somewhat simplified) style definitions targeting DevExpress Winforms look.

While we are prioritizing controls for Devolutions Remote Desktop Manager, we welcome contributions from the Avalonia community to add more DevExpress-style controls.

• Installation
• Styled Controls
  • ✅ Available in the current build
    • AutoCompleteBox
    • Button
    • ButtonSpinner
    • Calendar
      • CalendarButton
      • CalendarDatePicker
      • CalendarDayButton
      • CalendarItem
    • CheckBox
    • ColorPicker
    • ComboBox
      • ComboBoxItem
    • DataGrid
    • EditableComboBox (Custom control)
    • Expander
    • ListBox
      • ListBoxItem
    • NumericUpDown
      • ButtonSpinner
    • RadioButton
    • ScrollViewer
      • ScrollBar
    • Separator
    • TabControl
      • TabItem
    • TabPane
    • TagInput (Custom control (Ursa))
    • TextBox
    • TreeView
      • TreeViewItem
    • Window
  • 🚧 In progress ...
    • small improvements & fixes, some code cleanup
    • ContextMenu
    • SplitButton
  • 🔮 Next on the road map ...
    • vertical tabs

Installation

Avalonia 12 required. Packages 2026.6.17-avalonia12 and later require Avalonia 12. The last stable release compatible with Avalonia 11 is 2026.6.16.

Install the Devolutions.AvaloniaTheme.DevExpress package via NuGet:

Install-Package Devolutions.AvaloniaTheme.DevExpress

or .NET

dotnet add package Devolutions.AvaloniaTheme.DevExpress

In your App.axaml, replace the existing theme (e.g. <FluentTheme /> or <SimpleTheme />) with the DevExpress theme:

<Application ...>
  <Application.Styles>
     <DevolutionsDevExpressTheme />
  </Application.Styles>
</Application>

Note: Some global Styles will also be loaded by default, you can opt out by setting GlobalStyles to false (<DevolutionsDevExpressTheme GlobalStyles="False" />). GlobalStyles are also available as a separate tag <DevolutionsDevExpressThemeGlobalStyles /> to cover scenarios where consumers would like to scope them to some control instead of including them globally. This is may be necessary to prevent styles from "bleeding out" in cases where that might be undesirable.

Menu pack (menu controls only)

Use the menu pack when you only want DevExpress menu styling but not the full <DevolutionsDevExpressTheme /> (e.g. to give consistent Menu chrome to custom-branded sections of your app).

<Application ...>
  <Application.Styles>
    
    <FluentTheme />

    
    <StyleInclude Source="avares://Devolutions.AvaloniaTheme.DevExpress/Controls/MenuPack.styles.axaml" />
  </Application.Styles>
</Application>

Exact menu pack URI:

avares://Devolutions.AvaloniaTheme.DevExpress/Controls/MenuPack.styles.axaml

Prerequisites and caveats:

• The pack is designed to be layered over a foreign host theme without depending on host-owned menu resources. It vendors its own scroll-viewer theme and pins the arrow resources it consumes locally, so no application-wide Fluent prerequisite remains.
• The pack styles ContextMenu, MenuFlyoutPresenter, Menu, MenuItem, Separator, and the menu-specific helper styles (Menu.styles.axaml, Separator.styles.axaml, and the MenuItem Svg icon CSS styles).
• If you need full control coverage, use <DevolutionsDevExpressTheme /> instead.

Resource contract

All menu tokens live in a single shared file, Accents/MenuResources.axaml, which is included by both the full theme and the menu pack. There is one source of truth, so the pack can never drift from the full theme.

Two rules make the pack safe to layer over a host theme you do not control:

1. The pack's token keys are prefixed DevExMenu — those resources are owned by the pack and cannot collide with, or be silently overridden by, the host theme's keys.
2. Values are pinned literals, never aliases. Menu tokens do not resolve through generic theme-wide or Fluent-owned keys. A host theme that redefines e.g. MenuFlyoutPresenterBorderThemeThickness or FlyoutThemeMaxWidth cannot move menu visuals.

The pack also intentionally ships non-prefixed named and implicit control themes such as MenuTopLevelMenuItem, HorizontalMenuFlyoutPresenter, {x:Type MenuItem}, {x:Type Menu}, and {x:Type ContextMenu}. Those keys are not resource-name collisions: they are the pack's own design-time theme registrations, and they are intentionally exempt from the DevExMenu prefix rule.

Inherited from the host (by design):

None. Menu template dependencies are fully owned by the pack, including the vendored DevExMenuScrollViewer and the arrow resources it pins locally.

Typography and normal-state colours are pinned, not inherited. DevExMenuFontFamily / DevExMenuFontSize / DevExMenuFontWeight are owned by the pack, and the same applies to the normal-state DevExMenuItemBackground / DevExMenuItemForeground values. The point of the pack is that menus in a branded or opted-out section still match the platform-themed menus elsewhere in the same app; inheriting the host's font or colours defeated that. Pinning also keeps menu geometry identical across hosts.

Style-level sealing is applied in two selectors instead of one: popup rows are descendants of MenuFlyoutPresenter/ContextMenu/Menu, while menu-bar items are direct children of Menu. The popup-row geometry and the top-level bar geometry are different, so the seal pins the same typography and normal-state colour for both while preserving each item's own padding and bar height. The seal intentionally covers the normal state only; hover, pressed, selected, and disabled states are handled by template-child selectors in the MenuItem control theme.

This sealing lives in MenuPack.Sealing.styles.axaml and is included only by the standalone pack, not by the full DevolutionsDevExpressTheme. Inside the full theme, app-level Style overrides on menu items are expected to win, the same as for any other themed control. To override a pack-sealed property from a consuming app, your override selector must also match a pseudo-class (e.g. :not(:separator)) to reach the same StyleTrigger priority tier, and should live in a scope nested inside the one hosting the pack (Avalonia resolves same-priority ties by scope — inner wins — before declaration order).

The pack styles menu content only. It deliberately does not ship a Separator ControlTheme: that resource is keyed {x:Type Separator}, so merging it would restyle every separator in your app rather than just menu ones. Menu separators instead reuse the host's separator template — which is identical across Fluent, MacOS, Linux and DevExpress — with every template-bound property pinned inside the menu-scoped selector. A guard test asserts that adding the pack leaves non-menu separators byte-identical.

Overriding a token. Because tokens are prefixed, you can retarget any single value without affecting the rest of your app. The override must live in the same resource scope as the pack (or a descendant of it), because resource lookup walks up the tree and stops at the first match. If a StyleInclude is added on a UserControl but the override lives on the Window, the override is silently ignored.

<Application.Styles>
  <StyleInclude Source="avares://Devolutions.AvaloniaTheme.DevExpress/Controls/MenuPack.styles.axaml" />
</Application.Styles>

<Application.Resources>
  <SolidColorBrush x:Key="DevExMenuSeparatorBrush" Color="#ff0000" />
</Application.Resources>

The pack and the override must live in the same collection scope, or in a parent/child scope where the override is resolved before the pack is considered. In practice, the simplest pattern is to keep the pack in Application.Styles and the override in Application.Resources (or in the same UserControl.Resources scope as the pack).

Both rules are enforced by MenuPackContractTests in the visual test project, which asserts that every DevExMenu* token resolves identically under the full theme and under "pack over a foreign host", and that a hostile host theme cannot leak into any of them.

Styled Controls

Most of the images below are screenshots from the SampleApp test and demo pages - feel free to check out the code there for more detailed usage examples.

For an always up-to-date visual reference you can also browse the baseline screenshots.