WPF VS Introducing .NET Multi-platform App UI (MAUI)

Gear up, folks, and test drive this fresh-off-the-lab feature. And should you stumble upon any glitches along the way, don’t hesitate to reach out. Got a bug to report or feedback to give? Send them directly to our dotnet/wpf repository. We’re eager to hear from you, because together, we’re only going to make the experience even better!

There’s still room for improvement though. I should add, WPF on .NET Core consumes a lot of memory, due to a memory leak. It was logged by our COO as one of our users was doing a comparison.

WPF: Licencia MIT.

WPF is definitely not dead. It may not be the latest shiny thing, but it works, it is maintained (judging by https://github.com/dotnet/wpf or https://devblogs.microsoft.com/dotnet/wpf-on-dotnet-7/), and it is fully and officially supported on the modern .NET platform.

Feature: new WPF style for Windows 10

Okay apparently someone got it working with a simple patch: https://github.com/dotnet/wpf/issues/688

WPF is not abandoned (the last commit to its repo was today).

WPF (UI framework built on top of Direct3D): open (last commit: 2 days ago), still supported WinUI 1 (UI framework built on top of Direct3D): proprietary, supported until Jan 10 2023 WinUI 2 (UI framework built on top of Direct3D): open (last commit: 2 days ago), still supported WinUI 3 (UI framework build on top of Platform Uno): open (couldn't find v3 branch or repo), not yet released

It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.

Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.

[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup

[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)

While this is the quite endorsed by the community: https://github.com/dotnet/maui/discussions/339

I think the fundamental issue is that desktop Linux is way too fragmented. Not only just GTK2/3 and Qt but you have GNOME, KDE, XFCE, Cinnamon and then you have X11, Xorg, Wayland...

To be honest, all those craps are why desktop Linux never took off. I'm very safe to say MAUI for Linux will eventually renders components off its own using framebuffer and hardware acceleration APIs such as OpenGL or Vulkan just because of the market fragmentations...

If desktop Linux truly wants to get the attention, it will need to unify. Fixing dependency hell using Flatpak is the right direction.

There is an existing old fork of MAUI for Linux that uses GTK: https://github.com/jsuarezruiz/maui-linux

But, if you really want to add some value, luckily, Maui is an open source platform, the code is right there, dig into it, and learn how it works under the hood (it will also help you to learn a lot, trust me), you found something to be fixed and know how to do it? then do fix it and open a PR with the solution, you found a workaround to some issues? Then open a PR with the solution or share it with others.

Looking at the oft-mentioned 2.3K issues on the MAUI repo, I think there's a pretty even split a given issue will be one of these: valid, duplicate, user error, feature request. Seriously, just scroll through the first couple of pages. Maybe they need to control that better, but it seems far from representative of "MAUI bugs".

The official issue is already 3 years old... https://github.com/dotnet/maui/issues/34

I have some memory heavy pages which causing the problem because android never disposes transient pages: https://github.com/dotnet/maui/issues/14654

you mean like this: https://github.com/dotnet/maui/issues/4528 ?

MAUI (sucesor de Xamarin.Forms): Licencia MIT.

Github bug #11849Here