Make avalonia compile xaml pages per flavor #20069
CastelloBrancoTecnologia
started this conversation in
Ideas
Replies: 2 comments 4 replies
-
These are not the same things as what you are asking for. XPF for example really is WPF, it just uses Avalonia's rendering system. Which means it uses the actual WPF XAML compiler. Modern WinUI is handled by Uno https://github.com/unoplatform/uno Also: Obligatory XKCD |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Good news, Microsoft created a concept called xaml standard https://github.com/microsoft/xaml-standard Bad news, Microsoft gave up. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What do you think about enabling Avalonia to detect a XAML file by its “flavor” and compile it using Avalonia, WPF, WinUI, or MAUI—depending on the project’s needs?
All controls from these four platforms could be supported through a compatibility layer, allowing legacy systems from any of them to be integrated into new Avalonia projects.
The WPF part is already nearly complete through XPF,
and the MAUI support is currently being developed by the Avalonia team.
All that’s missing is WinUI.
Once integrated, everything could run on a single unified platform powered by Avalonia’s renderer, giving developers the ability to combine the best features of all these UI frameworks in a single application.
Beta Was this translation helpful? Give feedback.
All reactions