Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider using `PublishAot` for Mobile Platforms and Blazor WASM

See original GitHub issue

Android 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 GitHub Comments

1reaction

MichalStrehovskycommented, Jun 16, 2023

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

1reaction

eerhardtcommented, Jun 15, 2023

Note that https://github.com/dotnet/sdk/pull/29785 took the assumption that PublishAot=true implies DynamicCodeSupport=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.