// the find
OLonsdale/BlazorAvaloniaEmbed
Avalonia Widget running inside full Blazor Wasm App
A small sample that hosts an Avalonia view inside a Blazor WebAssembly page using Avalonia.Browser.Blazor, with one SchedulerVm instance bound two-way from both the Avalonia and Blazor sides. It is for developers who want to know whether Avalonia UI can sit beside Blazor components in the browser, and it works as a reference project, not a library.
The view model lives in a Shared project that both the Avalonia and Blazor apps reference, so SchedulerVm is written once and each UI is only a view over it. That is the right split for this kind of embed and the part worth copying. The project also answers a narrow question that is poorly documented, namely how Avalonia.Browser.Blazor gets wired into a Blazor WASM host, and it gives a concrete layout to start from. The footprint is small enough to read in one sitting.
The README is three lines. It never explains how the two-way binding is wired, what Bridge.cs does, or what the scheduler is meant to demonstrate, so a reader has to go through the source to learn the one thing the repo is about. Build output and IDE state are committed: AvaloniaApp/bin and obj, Shared/bin and obj, BlazorApp/obj and the .idea folder all appear in the listing, and no root .gitignore shows up to stop that happening again. There are no tests, and no LICENSE appears in the listing, so it is unclear whether the code can be reused at all. The last push was 2025-09-02, over a year before today, so it may not compile against current Avalonia and .NET releases.