Choose the application architecture
Model Integrations
Keep docking behavior consistent while choosing the notification and composition model.
Explore source ↗Capability
A framework-neutral model plus MVVM, ReactiveUI, Prism, INPC, ReactiveProperty, and Caliburn.Micro implementations lets applications adopt Dock without changing architecture.
- 01
Framework-neutral contracts
- 02
MVVM and INPC implementations
- 03
ReactiveUI and Prism integrations
- 04
Replaceable factory policy
How it composes
From intent
to working system.
Contracts
Interfaces define docks, dockables, factories, commands, and lifecycle.
Implementation
A chosen package supplies notification and base classes.
Application
The factory creates domain-specific documents and tools.
View
Dock.Avalonia consumes the common contracts.
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 Dock.Model.Mvvm<PackageReference Include="Dock.Model" Version="VERSION" /><PackageVersion Include="Dock.Model" Version="VERSION" />var factory = new DockFactory();var layout = factory.CreateLayout();
factory.InitLayout(layout);Layout = layout;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.