agentleFS
linuxdevellinuxdevel/Avalonia-skills/skills/avalonia/avalonia-deployment/SKILL.md

avalonia-deployment

Skill50 starsChanged 8 days agoMITView on GitHub

Use when packaging or deploying Avalonia apps for Windows, macOS, Linux, WebAssembly, Android, or iOS.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer the default AppKit macOS backend for new desktop apps.

    line 137

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Avalonia Deployment

Overview

Avalonia apps are .NET apps — standard dotnet publish with -r <RID> produces executables. Platform-specific packaging tools handle OS-native bundles.

Runtime Identifiers (RIDs)

PlatformRID
Windows x64win-x64
Windows ARM64win-arm64
macOS x64 (Intel)osx-x64
macOS ARM64 (Apple Silicon)osx-arm64
Linux x64linux-x64
Linux ARM64linux-arm64

Target Frameworks

11.312.0 / 12.1
Desktop / sharednet6.0+, netstandard2.0, .NET Frameworknet8.0 min, net10.0 recommended (no netstandard/.NET Framework)
Android / iOS / Mac Catalystnet8.0-android / net8.0-ios etc.net10.0-android / net10.0-ios / net10.0-maccatalyst (required)
Browsernet8.0-browser+net8.0-browser+ (net10.0-browser recommended)

Removed in 12: Avalonia.Browser.Blazor, Avalonia.Tizen, Avalonia.Direct2D1 (use Skia).

Basic Publish

# Self-contained single file (Windows)
dotnet publish -r win-x64 -c Release --self-contained true -p:PublishSingleFile=true

# Framework-dependent (requires .NET installed)
dotnet publish -r win-x64 -c Release --self-contained false

Windows

Options:

  1. MSIX — Use Visual Studio packaging project or msix-packaging-tool
  2. Installer (Inno Setup / WiX) — point at publish output
  3. Single EXE — PublishSingleFile=true + self-contained
<!-- .csproj for Windows -->
<PropertyGroup>
    <PublishSingleFile>true</PublishSingleFile>
    <SelfContained>true</SelfContained>
    <RuntimeIdentifier>win-x64</RuntimeIdentifier>
    <IncludeNativeLibrariesForSelfExtract>true</IncludeNativeLibrariesForSelfExtract>
</PropertyGroup>

macOS

# Publish
dotnet publish -r osx-arm64 -c Release --self-contained true

# Bundle as .app using dotnet-bundle tool:
dotnet tool install --global Dotnet.Bundle
dotnet msbundle -r osx-arm64 /p:CFBundleVersion=1.0.0

Info.plist properties in .csproj:

<PropertyGroup>
    <CFBundleName>MyApp</CFBundleName>
    <CFBundleIdentifier>com.mycompany.myapp</CFBundleIdentifier>
    <CFBundleVersion>1.0.0</CFBundleVersion>
    <NSHighResolutionCapable>true</NSHighResolutionCapable>
</PropertyGroup>

Notarization requires Apple Developer account + xcrun notarytool.

Linux

# AppImage
dotnet publish -r linux-x64 -c Release --self-contained true
# Then use appimagetool to wrap the publish output

# Debian package (.deb)
dotnet publish -r linux-x64 -c Release
# Use dpkg-deb or dotnet-deb NuGet tool
dotnet tool install --global dotnet-deb
dotnet deb -r linux-x64 -c Release

WebAssembly (WASM)

Separate project (MyApp.Browser.csproj):

<Project Sdk="Microsoft.NET.Sdk.WebAssembly">
    <PropertyGroup>
        <TargetFramework>net10.0-browser</TargetFramework>
        <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
    </PropertyGroup>
    <ItemGroup>
        <PackageReference Include="Avalonia.Browser" Version="12.1.4"/>
    </ItemGroup>
</Project>

(11.x) templates used Microsoft.NET.Sdk.BlazorWebAssembly / net8.0; Avalonia.Browser.Blazor is removed in 12. Entry point uses StartBrowserAppAsync("out"); App uses ISingleViewApplicationLifetime (unchanged in 12).

dotnet publish -c Release
# Output is static files (wwwroot/) — host on any static server

Android

<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFramework>net10.0-android</TargetFramework>  <!-- (11.x) net8.0-android / net9.0-android -->
    </PropertyGroup>
    <ItemGroup>
        <PackageReference Include="Avalonia.Android" Version="12.1.4"/>
    </ItemGroup>
</Project>
dotnet publish -f net10.0-android -c Release
# Produces .apk / .aab (AndroidPackageFormats)

Entry (12.0+): MainActivity : AvaloniaMainActivity + [Application] AndroidApp : AvaloniaAndroidApplication<App>; App sets IActivityApplicationLifetime.MainViewFactory (see avalonia-app-development). (11.x) AvaloniaMainActivity<App> + ISingleViewApplicationLifetime.

iOS / Mac Catalyst

<TargetFramework>net10.0-ios</TargetFramework>  <!-- (11.x) net8.0-ios / net9.0-ios -->
<PackageReference Include="Avalonia.iOS" Version="12.1.4"/>

Requires macOS + Xcode. Produces .ipa. iOS uses ISingleViewApplicationLifetime and the scene delegate lifecycle (12.0+; AvaloniaAppDelegate.Window is null after startup).

Mac Catalyst (12.0+) — same Avalonia.iOS project, add a target; needs dotnet workload install maccatalyst:

<TargetFrameworks>net10.0-ios;net10.0-maccatalyst</TargetFrameworks>
dotnet build -f net10.0-maccatalyst

Prefer the default AppKit macOS backend for new desktop apps; Catalyst is for UIKit-heavy / MAUI-hybrid scenarios.

Linux Wayland (12.1+, experimental)

Opt-in: add Avalonia.Wayland and call .UseWayland() on the AppBuilder. UsePlatformDetect() does not select it; X11 remains default.

SBOM (12.1+)

Avalonia 12.1.0+ packages ship a Software Bill of Materials listing the framework's NuGet packages (supports CRA/compliance work).

Trimming

Enable for smaller binaries — may break reflection-heavy code:

<PublishTrimmed>true</PublishTrimmed>
<TrimmerRootDescriptor>TrimmerRoots.xml</TrimmerRootDescriptor>

Watch for reflection in converters, ViewLocator. Compiled bindings (default ON in 12, opt-in in 11) avoid binding reflection and are trim-friendly; reflection bindings (ReflectionBinding) are not.

Community Deployment Tools

ToolNuGet / RepoPurpose
PupNet DeployGitHub: kuiperzone/PupNet-DeployCross-platform deployment: AppImage, Flatpak, deb, rpm, MSIX, zip
dotnet-debdotnet-deb toolGenerate Debian .deb packages
Dotnet.BundleDotnet.Bundle toolmacOS .app bundle + DMG creation
macOS.SparkleUpdater.AvaloniaGitHub: Deadpikle/macOS.SparkleUpdater.AvaloniaSparkle auto-update integration for macOS

PupNet Quick Start

dotnet tool install --global KuiperZone.PupNet
pupnet --help

# Build AppImage for Linux
pupnet -r linux-x64 -k AppImage

# Build MSIX for Windows
pupnet -r win-x64 -k Msix

# Build Setup.exe (Inno)
pupnet -r win-x64 -k Setup

PupNet reads a pupnet.conf in your project root. Handles icon conversion, desktop entries, version injection automatically.

Common Mistakes

  • macOS .app bundle missing NSHighResolutionCapable → blurry on Retina
  • Publishing without --self-contained to machines without .NET installed
  • WASM project must use ISingleViewApplicationLifetime, not IClassicDesktopStyleApplicationLifetime
  • Android/iOS heads left on net9.0-* with Avalonia 12 — needs net10.0-*
  • Referencing removed packages in 12 (Avalonia.Browser.Blazor, Avalonia.Tizen, Avalonia.Direct2D1)
  • Expecting UsePlatformDetect() to pick Wayland in 12.1 — requires Avalonia.Wayland + UseWayland()
  • Trimming with ViewLocator using Type.GetType() by string → types trimmed away; add trim roots

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.