-
Notifications
You must be signed in to change notification settings - Fork 310
AndroidX migration #80
Comments
@gianlucaparadise sorry for unrelated question, can you explain how exactly do you use the GalaSoft.MvvmLight.Platform.AndroidSupport package, please? |
@MichaelShapiro for example, we use the Since the |
Oh, ok, I see.. so it is only for certain specific things. I actually use JimBobBennett.MvvmLight.AppCompat lib to make MVVMLight compatible with Android Support Libs (at least for navigation purposes). As far as I understand the Android X is still in preview, and I personally not migrating until it's all released officially. But this project, MVVMLight, seems to not being maintained anymore, unfortunately. At least I do not see any responses from Laurent for a long time now :( |
As far as I know, AndroidX is not in preview since 1.0.0 (September 2018). Support Libraries are not maintained anymore and Google recommend using the AndroidX libraries in all new projects.
Do you refer to Anyway, I created a pull request with the migration #81. |
@gianlucaparadise - I am so sorry, you are correct - I meant to say that Xamarin.AndroidX is in preview. As a result I am holding off on migration in the production environment. |
That's true, but in my opinion, a preview version of the |
I updated the pull request #81 with the latest stable AndroidX packages. |
Hi @MichaelShapiro , Thanks. |
I need this functionality as well. Is this project dead? @gianlucaparadise did you just end up forking the project and making the changes for yourself? |
@andrewescutia Yes, I ended up forking the project and creating a temporary Nuget to be used until the official one is released. In case you need them:
|
Is it planned a migration from Android Support to AndroidX for the
GalaSoft.MvvmLight.Platform.AndroidSupport
package?In my opinion, this is a really blocking issue because it blocks the migration to AndroidX. The migration is necessary in order to use the latest libraries for the Android Ecosystem.
The text was updated successfully, but these errors were encountered: