Fabulous.Avalonia.DataGrid 10.0.4

dotnet add package Fabulous.Avalonia.DataGrid --version 10.0.4
                    
NuGet\Install-Package Fabulous.Avalonia.DataGrid -Version 10.0.4
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Fabulous.Avalonia.DataGrid" Version="10.0.4" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Fabulous.Avalonia.DataGrid" Version="10.0.4" />
                    
Directory.Packages.props
<PackageReference Include="Fabulous.Avalonia.DataGrid" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Fabulous.Avalonia.DataGrid --version 10.0.4
                    
#r "nuget: Fabulous.Avalonia.DataGrid, 10.0.4"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Fabulous.Avalonia.DataGrid@10.0.4
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Fabulous.Avalonia.DataGrid&version=10.0.4
                    
Install as a Cake Addin
#tool nuget:?package=Fabulous.Avalonia.DataGrid&version=10.0.4
                    
Install as a Cake Tool

DataGrid for Fabulous.Avalonia

The DataGrid control is a cross-platform view that displays repeating data in a customizable grid. The control can be styled, templated and bound.

The data grid needs to be bound to an observable collection in a view model that can be found in a related data context. Based on AvaloniaUI DataGrid.

How to use

  • Add the Fabulous.Avalonia.DataGrid package to your project.
  • Open Fabulous.Avalonia at the top of the file where you declare your Fabulous program (eg. Program.stateful).
open Fabulous.Aavalonia

open type Fabulous.Avalonia.View
Using the DataGrid Widget

Now you can use the DataGrid and AutoGeneratedDataGrid widgets in your Fabulous app as follows:

VStack() {
    DataGrid(model.People)

    (CustomDataGrid(model.People) {
        DataGridTextColumn("Name", Binding("Name"))
        DataGridTextColumn(TextBlock("Age"), Binding("Age"))
        DataGridCheckBoxColumn("IsMale", Binding("IsMale"))
    })
        .gridLinesVisibility(DataGridGridLinesVisibility.Horizontal)
        .borderThickness(1.0)
        .borderBrush(SolidColorBrush(Colors.Gray))
}

A full, working example is included in the DataGridPage sample

Additionally, we have the Fabulous Discord server where you can ask any of your Fabulous related questions.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
10.0.4 118 10/12/2026
10.0.3 118 9/30/2026
10.0.2 102 9/27/2026
10.0.1 162 9/7/2026
10.0.0 136 8/24/2026
3.0.0-pre9 214 1/17/2025
3.0.0-pre8 208 12/27/2024
3.0.0-pre7 201 11/27/2024
3.0.0-pre6 221 5/20/2024
3.0.0-pre5 231 5/17/2024
3.0.0-pre4 230 4/19/2024
3.0.0-pre3 257 4/13/2024
3.0.0-pre2 230 3/31/2024
3.0.0-pre13 460 11/19/2025
3.0.0-pre12 212 5/24/2025
3.0.0-pre11 267 4/7/2025
3.0.0-pre10 196 2/28/2025
3.0.0-pre1 224 3/23/2024
2.4.0 325 4/7/2025
2.4.0-pre1 224 2/9/2024
Loading failed

### Added
- Add unit tests for `Reconciler.update`, covering that it forwards exactly one diff to `IViewNode.ApplyDiff`, correctly reports scalar-attribute added/unchanged/changed cases, and handles a missing previous widget and an attribute-less widget pair (Repo Assist, #1341).
- Add unit tests covering `WidgetDiff.ScalarChanges` diffing (Added/Removed/Updated cases, empty prev/next, and the `SkipRepeatingScalars` duplicate-key behavior) (Repo Assist, #1311).
- Add unit tests for `WidgetDiff.EnvironmentChanges`, covering empty prev/next, all-Added/all-Removed cases, `Updated` on differing values, no-op on identical values, disjoint key sets, and the `SkipRepeatingScalars` duplicate-key dedup behavior (Repo Assist, #1312).
- Add unit tests for `WidgetDiff.WidgetChanges`, covering Added/Removed/Updated/ReplacedBy cases, empty prev/next, no-op on identical widgets, `canReuseView` true/false branching, and disjoint attribute sets (Repo Assist, #1316).
- Add unit tests for `WidgetDiff.WidgetCollectionChanges` and `WidgetDiff.WidgetCollectionItemChanges` diffing, covering attribute-level added/removed/updated collection attributes and item-level insert/replace/update/remove behavior for collections of differing lengths (Repo Assist, #1332).

### Changed

- Simplify `Cmd.map`'s closure composition to avoid allocating an extra intermediate function per effect on every call (Repo Assist, #1357).
- Implement `CollectionBuilder.YieldFrom` using `MutStackArray1.addMut` directly (addressing a `TODO` left in the code), avoiding the intermediate `Seq.map`/`Seq.toArray` allocations previously used to compile a sequence of widgets (Repo Assist, #1357).
- Revise the Windows development instructions in the MAUI tutorial and get-started guide, the MAUI/Avalonia tutorials and get-started guides, and the migration guide, and update the website index page and header.
- Change the MAUI template (`Fabulous.MauiControls.Templates`) to generate an unpackaged Windows project by default: `NewApp.fsproj` now sets `WindowsPackageType=None` with the FS0226 workaround (`WindowsAppSdkUndockedRegFreeWinRTInitialize=false`), and `Properties/launchSettings.json` uses the `Project` command instead of `MsixPackage`. F5 debugging in Visual Studio and `dotnet run` now work on Windows without manual edits. This only affects projects created with this template version or later; projects generated earlier keep their current setup and can be converted by hand as described in the MAUI tutorial. To use MSIX packaging in a new project, set `WindowsPackageType=MSIX` and use `MsixPackage` in `launchSettings.json` (#1408, #1409).
- Update the MAUI tutorial for the unpackaged Windows default: keep the manual conversion steps for projects created before 10.0.4, fix the "Why not packaged (MSIX)?" anchor links, and document how to switch back to a packaged build (#1410).
- Update the `FSharp.Maui.WinUICompat` README to reflect that the Fabulous MAUI template now generates an unpackaged Windows project by default, while the stock MAUI template and earlier Fabulous templates still use `MsixPackage` (#1412).
- Change the MAUI samples to build as unpackaged Windows applications, matching the updated MAUI template: each sample's `.fsproj` now sets `WindowsPackageType=None` with the FS0226 workaround, and `Properties/launchSettings.json` uses the `Project` command instead of `MsixPackage` (Repo Assist, #1411, #1413).

### Fixed

- Correct the `Cmd` module migration section in `docs/guides/migration.md` (Repo Assist, #1391).