xaml-csharp-development-skill-for-avalonia

WinUI CollectionViewSource Grouping and ItemSource Patterns to Avalonia

Table of Contents

1. Scope and APIs
2. Concept Mapping
3. Conversion Example
4. Migration Notes

Scope and APIs

Primary WinUI APIs:

• CollectionViewSource, IObservableVector, IncrementalLoadingCollection

Primary Avalonia APIs:

• CollectionView, ItemsSource, CollectionViewSource-like VM shaping

Concept Mapping

WinUI idiom	Avalonia idiom
WinUI control/template/state pipeline	Avalonia control theme/style/selector pipeline
x:Bind or {Binding} data flow	{CompiledBinding ...} and typed x:DataType flow
WinUI layout/render invalidation model	Avalonia InvalidateMeasure/InvalidateArrange/InvalidateVisual model

Conversion Example

WinUI XAML:

<Page
    x:Class="MyApp.Views.SamplePage"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:local="using:MyApp.Controls">
  <ListView ItemsSource="{x:Bind ViewModel.GroupedItems.View}" />
</Page>

WinUI C#:

var view = new ListView();

Avalonia XAML:

<UserControl xmlns="https://github.com/avaloniaui"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             xmlns:vm="using:MyApp.ViewModels"
             xmlns:local="using:MyApp.Controls"
             x:DataType="vm:SampleViewModel">
  <ListBox ItemsSource="{CompiledBinding GroupedItems}" />
</UserControl>

Avalonia C#:

var list = new ListBox { ItemsSource = viewModel.GroupedItems };

Migration Notes

1. Start by porting behavior and state contracts first, then restyle and retune visuals.
2. Prefer typed compiled bindings and avoid reflection-heavy dynamic binding paths.
3. Keep UI-thread updates explicit when porting WinUI async/event flows.

This site is open source. Improve this page.