[Question] Official stance on community contributions about Linux-support #31649
|
Seeing that most Linux support–related issues have been closed, I assume that the MAUI team does not plan to officially support Linux. If the community were to develop Linux support for MAUI, would there be a possibility for it to be merged into the main repository? In addition, there is a discussion that has received over 500 upvotes and more than 700 👍 reactions, which suggests that there is strong support from the community. Are you willing to accept contributions from the community in this area? See also: https://github.com/dotnet/maui/issues?q=label%3Aplatform%2Flinux |
Replies: 6 comments
|
Developing a Linux backend of layout and controls for .NET MAUI is not on our roadmap. We recognize the interest and value of this to the product and developer experience, and welcome contributions that would enable this experience. In considering future backends, @PureWeen prototyped developing backends in their own repository. This is the pattern we'd like to follow and evolve. https://github.com/PureWeen/maui.wpf |
|
In continuation of what David says above, there is already a somewhat progressed version, active, for Linux by one of our team members @jsuarezruiz right here: https://github.com/jsuarezruiz/maui-linux |
This is my first time hearing about maui.wpf, thank you for pointing it out.
I am familiar with maui-linux (as I am one of its contributors), and I was wondering: once it reaches a production-ready stage, is there any chance it could be merged into the main project (here)? |
|
Hi everyone, Running .NET MAUI apps in the browser guarantees execution on any device, without providing official support. All that's needed is for the OS to be able to run a browser, and you're done. |
|
I thought MAUI was a serious project that would replace stuff like UWP, Xamarin and be truly cross-platform. I guess UNO or Avalonia are the real alternatives if you are so unfortunate to be stuck developing with Microsoft software :-/ |
|
Wanted to let folks on this thread know there's now something concrete to try. Over in dotnet/maui-labs we've been building experimental platform backends, including a GTK4 backend for Linux and a native macOS AppKit backend (macOS without Mac Catalyst). Both also ship a Linux (GTK4) — README + setup:
macOS (AppKit) — README + setup:
All published as Status — please read before building on it:
Building these has also been a good exercise of the extensibility work tracked in #34099 — the places MAUI can stop actively preventing third-party platforms, without the team having to own or officially support them. Give the experimental backends a try, file issues in maui-labs, and let us know what's working and what's missing — with the understanding above about where things stand. |
Wanted to let folks on this thread know there's now something concrete to try. Over in dotnet/maui-labs we've been building experimental platform backends, including a GTK4 backend for Linux and a native macOS AppKit backend (macOS without Mac Catalyst). Both also ship a
BlazorWebViewhost — via WebKitGTK on Linux and WKWebView on macOS — so the "run your .NET business logic natively + a Blazor UI in a native WebView" scenario works on each.Linux (GTK4) — README + setup:
Microsoft.Maui.Platforms.Linux.Gtk4— the backendMicrosoft.Maui.Platforms.Linux.Gtk4.BlazorWebView— BlazorWebView on WebKitGTKMicrosoft.Maui.Platforms.Linux.Gtk4.Essentials— Essentials APIsMicrosoft.Maui.Platforms.…