DevExpress WinForms Ribbon and Bars

DevExpress.XtraBars is one library that ships both Ribbon UI (RibbonControl + RibbonForm + RibbonStatusBar + BackstageViewControl) and the classic Bars system (BarManager + Bar + BarDockControl). Both stacks share the same items/links architecture — every command is a non-visual BarItem (BarButtonItem, BarCheckItem, BarEditItem, BarSubItem, BarStaticItem, BarHeaderItem, RibbonGalleryBarItem, …) and every visible button/dropdown is a BarItemLink referencing one of those items. The same BarButtonItem can appear in a ribbon page group, the QAT, the page header area, a popup menu, and a status bar at once; clicking any link fires the item's one ItemClick handler.

WinForms vs WPF terminology — three corrections to the prompt:

1. The host form for a Ribbon must inherit from DevExpress.XtraBars.Ribbon.RibbonForm (not ThemedWindow — that is WPF). RibbonForm derives from XtraForm and integrates the ribbon into the non-client area for QAT + caption bar items.
2. There is no separate MainMenuControl / StatusBarControl / ToolBarControl in WinForms — those names belong to the WPF Bars stack. In WinForms, BarManager hosts a collection of Bar objects; the bar assigned to BarManager.MainMenu plays the main-menu role, BarManager.StatusBar plays the status-bar role, and any other Bar with DockStyle = Top/Bottom/Left/Right is a toolbar.
3. There is no WinForms-native MVVM framework in DevExpress on par with WPF's. The cross-platform DevExpress.Mvvm package (separately installable) does work in WinForms — you can use BindableBase, DelegateCommand, and INotifyPropertyChanged with BindingSource to data-bind BarItem.Caption/Enabled/Visible/Down, and a Bind-style helper to wire ItemClick to a ICommand. This is the pragmatic substitute for ribbon MVVM in WinForms.

When to Use This Skill

(The detailed API surface per task is in the Navigation Guide below.)