Is this project still alive?

[Gabboxl]

Last sign of life was 9 months ago, is this project still being maintained?
Would like some PRs to be merged and some issues to be resolved, like #1054. If this repo reached EOL I will consider starting a fork trying to keep it going.

[huoyaoyuan]

The core developer Sergio is busy for another project (CsWinRT 3.0). There's nobody for backup to maintain this repo currently.

[JosHuybrighs]

This might get problematic. Starting from November Google requires all apps to support 16k pages. MAUI apps must run with .NET 9 for that. Not sure if really needed but I would think that we then need .NET 9 support for the CommunityToolkit package when used in MAUI.

[huoyaoyuan]

Individual library doesn't need to be targeting newer framework to get support for runtime feature.

[Sergio0694]

Yeah there's no security impact here for consumers. Security fixes and the .NET support policy itself doesn't apply to libraries, only to actual applications. You could be using a .NET 5 library on .NET 10 and things would still be fine. Of course, you would be missing out on features and stuff, but I'm saying strictly from a security standpoint, it's fine (even if, say, .NET 5 itself is EOL, it doesn't matter).

[JosHuybrighs]

@huoyaoyuan @Sergio0694
Not sure if we are talking about the same subject.
I brought this up because I released a MAUI app on Google Play and got a message back saying that from November all updated apps must support 16KB pages. This is about the alignment of the different segments in for instance a shared library that is bundled with the app. There are quite a lot of these libraries in my package but I have to conclude that one or more of these libraries don't have the alignment correctly set to 16KB. So I have to find out which libraries are incorrect.
When examining this, I was wondering whether this would be the case with the CommunityToolkit.Mvvm package that is released for .NET 8. Because I learned that .NET 9 will guarantee 16KB alignment I was wondering whether something has to be done for the toolkit.
Good news: Apparently not because when I read the headers of the generated CommunityToolkit.Mvvm.dll.so file with readelf it looks like all LOAD segments of the toolkit library are correctly aligned at 0x4000 (16KB).
I don't know enough about what is happening behind the scenes when building in Visual Studio and therefore I would like to learn if the fact that the library is OK is because of the NUGET package taking care of this or if it is Visual Studio setting up the correct alignment when building any imported .NET library for .NET 9.

[huoyaoyuan]

I brought this up because I released a MAUI app on Google Play and got a message back saying that from November all updated apps must support 16KB pages. This is about the alignment of the different segments in for instance a shared library that is bundled with the app.

The requirement is about native library (.so and NativeAOT compiled assembly), not managed dll.

When examining this, I was wondering whether this would be the case with the CommunityToolkit.Mvvm package that is released for .NET 8. Because I learned that .NET 9 will guarantee 16KB alignment I was wondering whether something has to be done for the toolkit.

A managed library released for .NET X means it references the managed API of .NET X, and nothing more. It's not coupled to any .NET version, just requires the version or higher.

I don't know enough about what is happening behind the scenes when building in Visual Studio and therefore I would like to learn if the fact that the library is OK is because of the NUGET package taking care of this or if it is Visual Studio setting up the correct alignment when building any imported .NET library for .NET 9.

A .NET 9 Android application will compile its every managed library with .NET 9 toolchain. The targeting framework of managed library is just a virtual API contract and has no effect at native building stage.

In other words, there's no pre-processing for Android or any other platform for a managed-only NuGet package. All the Android-specific processing happens after all the libraries are gathered into a .NET 9 application, and processed altogether.