Each package is named for what you install. Most Application source folders
and namespaces keep the older Views name; independent navigation packages use
Runic.Navigation.
| Package | Source folder | Namespace |
|---|---|---|
Runic.Application |
packages/dotnet/Runic.Application.Views |
Runic.Application.Views |
Runic.Application.CsWebUi |
packages/dotnet/Runic.Application.Views.CsWebUi |
Runic.Application.Views.CsWebUi |
Runic.Application.Desktop |
packages/dotnet/Runic.Application.Desktop |
Runic.Application.Views.Desktop |
Runic.Application.ReactiveUI |
packages/dotnet/Runic.Application.Views.ReactiveUI |
Runic.Application.Views.ReactiveUI |
Runic.Application.Testing |
packages/dotnet/Runic.Application.Testing |
Runic.Application.Testing |
Runic.Application.Wpf |
packages/dotnet/Runic.Application.Wpf |
Runic.Application.Views.Wpf |
Runic.Navigation |
packages/dotnet/Runic.Navigation |
Runic.Navigation |
Runic.Navigation.Wpf |
packages/dotnet/Runic.Navigation.Wpf |
Runic.Navigation.Wpf |
Runic.Navigation.ReactiveUI |
packages/dotnet/Runic.Navigation.ReactiveUI |
Runic.Navigation.ReactiveUI |
Runic.Navigation.ReactiveUI.Reactive |
packages/dotnet/Runic.Navigation.ReactiveUI.Reactive |
Runic.Navigation.ReactiveUI.Reactive |
- Incremental WPF migration
- ReactiveUI 26 capabilities and Avalonia comparison
- Views build targets, shipped in the
Runic.Applicationpackage dotnet runicdevelopment and doctor commands@runic-artifex/views: the shared browser runtime and mock Bridge for generated clients- React package, Vue package, Svelte package and Angular package
The examples show complete Window composition, generated client use, browser mount lifecycle, and frontend integration.