Did you consider using the scheme that ILLink/R2R/SingleFile use right now?

It feels like it would make the sequencing most "standard". We'd probably need to wait for the new SDK to flow to this repo but we just did an upgrade and we could do another one.

This moves us in that direction - now this target will be sequenced appropriately - and we can change from AfterTargets to DependsOnTargets in a later change. I'm looking at the native aot targets all-up to see if there's other logic that needs cleanup, but wanted to start with this piece.

(The CI failures look related)

/azp run runtime-ioslike

/azp run runtime-extra-platforms

@ivanpovazan is there going to be any work required in the iOS SDK as a result of this change?

@ivanpovazan is there going to be any work required in the iOS SDK as a result of this change?

No, because we opt-out from NativeAOT Publish targets and handle them differently:
https://github.com/xamarin/xamarin-macios/blob/8d57fe69ca1d9d63c8da2c9b5672eda4ea69ab4d/dotnet/targets/Xamarin.Shared.Sdk.props#L189

/azp run runtime-extra-platforms

/azp run runtime-android

I think this is ready to go - runtime-extra-platforms failures look unrelated (fixing some of them in #124582). PTAL @ivanpovazan @MichalStrehovsky @agocke

Can you also just run this locally and eyeball the target flow in the MSBuild binlog? Not to say that I don't trust CI... but I don't trust CI.

Maybe building the runtime with this change is good enough?

Target ordering matches my expectations:

Before:

After: