Skip to content

Fix notification functionality in Avalonia#4864

Open
Gabriel Dufresne (GabrielDuf) wants to merge 1 commit into
mainfrom
avalonia-notification
Open

Fix notification functionality in Avalonia#4864
Gabriel Dufresne (GabrielDuf) wants to merge 1 commit into
mainfrom
avalonia-notification

Conversation

@GabrielDuf
Copy link
Copy Markdown
Contributor

Summary

System (toast) notifications never appeared in the Avalonia app, while they work in the WinUI build. This wires the Windows App SDK into the Avalonia project and fixes the reflection bridge so toasts fire for the same events WinUI covers. #4861

Changes

  • csproj: reference Microsoft.WindowsAppSDK 1.7 (Windows-only), mirroring WinUI's unpackaged/self-contained setup; add BuiltInComInteropSupport=true (needed for WinRT activation), EnableCoreMrtTooling=false (drops the VS-only MSIX/PRI tooling that broke CLI builds), and suppress the MVVMTK0045 CsWinRT false-positive.
  • bridge: fix the projection assembly names; resolve the parameterless Register() overload; subscribe to NotificationInvoked before Register(); and resolve builder overloads (e.g. AddText) by argument type.

Coverage

Achieves parity with WinUI — operation progress/success/error, updates-available, upgrading-packages, self-update-available, and new-desktop-shortcuts notifications, plus toast click/button actions. Windows uses the App SDK bridge; macOS uses the existing osascript bridge; Linux falls back to the in-app banner (unchanged).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant