New commits in migueldeicaza/MonoTouch.Dialog:

* migueldeicaza/MonoTouch.Dialog@f500f9a Bump to .NET 8.

Diff: https://github.com/migueldeicaza/MonoTouch.Dialog/compare/94359c74ef481ce7b5daa28b890f35a6e77d94c8..f500f9a48dbf856c693b255078e1507cf1e8edde

New commits in spouliot/Touch.Unit:

* xamarin/Touch.Unit@5739ade Bump to .NET 8.

Diff: https://github.com/spouliot/Touch.Unit/compare/8d80e1f10414ec85afa14c8c45a05334eb37c6dd..5739adefc261b7bfeb70ff718c7b2d97bdfa42ee

…eAOT.

This contributes towards xamarin#17339.

…e we're using.

…e NativeAOT (aka CoreCLR) is a possibility now

… using NativeAOT

…t set it first.

Might not be necessary: dotnet/runtime#86753

…ernative implementation instead.

The Runtime.GetAssemblyLocation method is only used for diagnostic purposes, so the
exact value returned doesn't matter all that much, as long as it makes sense.

… to be removed for NativeAOT

… NativeAOT.

Rewrite a few asserts, since NUnitLite isn't actually trimmer-safe, and some collection
asserts don't work with NativeAOT.

…veAOT.

…ativeAOT already does something equivalent

…executable

…LC doesn't support executing after ILLink.

Currently, NativeAOT is implemented as a replacement (of sorts) for ILLink. However,
we need to execute both, and in order to do that, we force our own logic to execute
to determine what ILC does.

This might be improved in the future. Ref: dotnet/runtime#87187.

…okes

…rom ILLink

…ll assemblies

…abled

…and use them ourselves.

…hen using NativeAOT (and warn if someone asks otherwise).

…get the correct BCL libraries.

This is because NativeAOT contains swift code, and we'd have to add code to
embed the Swift libraries in any apps that target early OS versions. We could
eventually implement this, but let's wait and see if there's a demand first.

… supports.

This matches how NativeAOT works for other platforms.

…sing NativeAOT.

…NativeAOT.

… build when using NativeAOT.

…7 tests.

We had to bump NUnitLite and Touch.Unit's TargetFramework properties to
net8.0-* (otherwise projects using NativeAOT fails if these projects are
referenced), which means they can't be used from .NET 7 (aka our .NET 7
tests).

So just don't reference NUnitLite and Touch.Unit in this test.

… waiting for a dotnet/runtime fix.

…, we need a few upstream fixes.

We can fix this better once this fix reaches us:

    dotnet/runtime#87813

because then we can set the ICU data file at build time (to a relative path).