Data-driven command systems
MVVM & Runtime Merging
Let features contribute commands while the application retains one coherent ribbon.
Explore source ↗Capability
Definition and view-model types, command catalogs, two-way runtime state, and merge policies let modules contribute or reorder tabs, groups, and items without owning the ribbon shell.
- 01
XAML, MVVM, and hybrid composition
- 02
Command catalog abstraction
- 03
TabsSource, GroupsSource, and ItemsSource
- 04
Pluggable merge policies and ordering
How it composes
From intent
to working system.
Contribute
Application modules publish definitions or view-model collections.
Merge
Stable ids, order, and policy reconcile contributions.
Bind
The control observes command and two-way state services.
Present
One adaptive ribbon materializes the merged runtime model.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package RibbonControl.Core<PackageReference Include="RibbonControl.Core" Version="VERSION" /><PackageVersion Include="RibbonControl.Core" Version="VERSION" /><ribbon:Ribbon TabsSource="{CompiledBinding Ribbon.Tabs}" CommandCatalog="{CompiledBinding CommandCatalog}" SelectedTabId="{CompiledBinding Ribbon.SelectedTabId, Mode=TwoWay}" QuickAccessItems="{CompiledBinding QuickAccessItems}" />Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.