Consider using `PublishAot` for Mobile Platforms and Blazor WASM
See original GitHub issueAndroid currently uses the property AotAssemblies
. PublishAot
seems to do the same thing. Maybe we should accept either for Android, to provide uniformity. Same with Blazor, which uses RunAOTCompilation
.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:35 (34 by maintainers)
Top Results From Across the Web
Host and deploy ASP.NET Core Blazor WebAssembly
Learn how to host and deploy Blazor WebAssembly using ASP.NET Core, Content Delivery Networks (CDN), file servers, and GitHub Pages.
Read more >Dotnet ahead-of-time: PublishReadyToRun vs PublishAot ...
It's quite hard to understand the concept by just reading the documentation. What is the difference between the PublishReadyToRun vs PublishAot?
Read more >Blazor Server or Blazor WASM with ASP.NET Core Hosted
One advantage of using Blazor WASM is that it can reduce the load on the server since most of the processing is done...
Read more >Blazor Hybrid Web Apps with .NET MAUI
NET MAUI Blazor. MAUI is a cross-platform framework for creating native mobile and desktop apps with C# and XAML. MAUI uses a single...
Read more >Let's build an app with .NET MAUI and Blazor - YouTube
Showcasing migrating a Blazor WASM PWA to .NET MAUI and Blazor Hybrid.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s not just DynamicCodeSupport=false. PublishAot also enables single file analyzer, trimming analyzer, AOT analyzer, disables runtimeconfig.json generation, etc. We’ll have to update pretty much every use of this property within the SDK repo to not do the thing it’s doing if UseMonoRuntime=true.
https://github.com/dotnet/runtime/pull/74038#issuecomment-1217419038 https://github.com/dotnet/runtime/pull/74038#issuecomment-1217428786
Note that https://github.com/dotnet/sdk/pull/29785 took the assumption that
PublishAot=true
impliesDynamicCodeSupport=false
. This is true for coreclr’s “Native AOT” support, but it doesn’t hold true for Mono’s AOT support. You can “Publish AOT”, but still support “Dynamic Code”.We will have to rectify this assumption when we start using the
PublishAot
MSBuild property for Mono scenarios like Android and Blazor WASM.