-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create installable artifacts for Blazor hybrid desktop apps for Windows and macOS #2534
Comments
Thanks for contacting us. |
Hey. We had some discussions about Apple Silicon yesterday and this story came up. Just wanted to clarify that in order to release an application to the Apple Store, these applications need to be universal (i.e. the native binaries need to be universal supporting both x64 and arm64). So we might need a story here for publishing with a osx-x64-arm64 rid or something like that. |
@rconard I don't think this should be tracked in this repo, as it's a broader work. Is there any other issue tracking this we can dupe this with? |
Scoping out Linux for .NET 6. We expect Linux support to come later. |
@danroth27 Can we get another issue i.e. user story for Linux then? The related epic dotnet/aspnetcore#27217 links to this issue with the title: "Create installable artifacts for Blazor hybrid desktop apps for Windows, macOS, and Linux". When Linux was scoped out, we Linux users would need a new issue to follow 😉 |
@danroth27 why? are there some specific challenges to make this work on Linux? Anything community could help with? |
It's really a scoping decision for .NET MAUI in .NET 6. .NET MAUI is an evolution of Xamarin Forms, which currently has official support for Android, iOS, and UWP. .NET MAUI will add Windows desktop support with WinUI, and macOS support. Linux just didn't fit for .NET 6, but we absolutely still plan to do it. Blazor will run wherever .NET MAUI runs. Adding @davidortinau from the .NET MAUI team in case he wants to add anything. |
Would this also include things like Auto update features? |
Hopefully there isn't much, or any, Blazor-specific work here. The work is to verify that MAUI publishing scenarios work equally will with Blazor on all platforms. Separately we would need to make sure that Windows-specific publishing works for WPF and WinForms Blazor apps, such as ClickOnce, and Windows Application Packaging Projects. |
Also see #4329 |
Just looked at the roadmap for .net 7 - will this work item and dotnet/runtime#44736 help to develop native MAUI mac apps without using Mac Catalyst? We have ported part of our app to MAUI but we are stuck with Electron because it is not straightforward to use all native MacOS features through Catalyst. |
Hi @ErikApption
No, .NET MAUI's support for macOS is based on Catalyst and there aren't any plans to change that as far as I know.
I'd like to understand better what Catalyst limitations you're running into. Can you share more details on that? |
Closing as this is tracked separately. |
Here's the Mac Catalyst publish tracking issue: #5197 |
Summary
As a [developer], I want to [create installable artifacts for my Blazor hybrid desktop app] so that [I can distribute my app].”
The text was updated successfully, but these errors were encountered: