Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork3
A .NET MAUI plugin that provides helpers to make your transition from Xamarin.Forms to .NET MAUI easier
License
jfversluis/Plugin.Maui.FormsMigration
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
Plugin.Maui.FormsMigration provides helpers to make your transition from Xamarin.Forms to .NET MAUI easier.
Available onNuGet.
Install with the dotnet CLI:dotnet add package Plugin.Maui.FormsMigration, or through the NuGet Package Manager in Visual Studio.
The supported platforms for this library are Android, iOS and Windows.
This library consists of three APIs that you can use for different scenarios:
Each of these APIs will have their own way of using it. You can find the specifics below, or have a look at thesample application that is included in this repository.
Note
These APIs are meant for transition scenarios only. Use these APIs to retrieve data that is previously stored by your legacy Xamarin application and save them in a place where .NET MAUI can access that data from that point on. This is also the reason that these APIs are read-only.
With Xamarin and Xamarin.Forms you had the possibility to save simple types through theProperties API like so:Application.Current.Properties ["id"] = someClass.ID;. In .NET MAUI, this is no longer possible.
To help you transition from Xamarin to .NET MAUI, this library offers theLegacyApplication API to still be able to access previously saved properties. From there, save them through a newer API that is available in .NET MAUI. An example could be to use thePreferences API. See a simple example below.
intid;if(LegacyApplication.Current.Properties.ContainsKey("id")){id=(int)LegacyApplication.Current.Properties["id"];Preferences.Set("id",id);}
Note
For this API to work properly, you will have to make sure that the application identifier (or bundle identifier) is the same between your legacy Xamarin app and .NET MAUI app. This is needed so that the app gets installed in the same container on the operating system, which is needed to be able to read the property values that were stored previously.
Also see thisMicrosoft Learn Docs page for more information.
TheSecureStorage API is still available in .NET MAUI the same as it is in Xamarin and Xamarin.Forms. However, the name of the store where values were stored and some other details have changed which causes the .NET MAUI version of your app to not being able to retrieve the previously saved secure storage information.
With theLegacySecureStorage you can retrieve the previously saved information in the secure storage of your legacy Xamarin application. From there you should resave them through the .NET MAUI secure storage API. An example of how to use this API can be found below.
// The code below assumes that there is a secure value saved with the key "oauth_token". Replace this key// with any value(s) you have stored in your legacy Xamarin app to get them out.stringoauthToken=awaitLegacySecureStorage.GetAsync("oauth_token");boolresult=LegacySecureStorage.Remove("oauth_token");awaitSecureStorage.SetAsync("oauth_token",oauthToken);
Note
For this API to work properly, you will have to make sure that the application identifier (or bundle identifier) is the same between your legacy Xamarin app and .NET MAUI app. This is needed so that the app gets installed in the same container on the operating system, which is needed to be able to read the secure store values that were stored previously.
Warning
For iOS, make sure you have aEntitlements.plist with the following entry:
<key>keychain-access-groups</key>
<string>$(AppIdentifierPrefix)$(CFBundleIdentifier)</string>
$(AppIdentifierPrefix)$(CFBundleIdentifier) can stay in place and will be replaced at build time or you can replace it with a hardcoded value.Additionally make sure that theEntitlements.plist file is set in the Custom Entitlements field for Bundle Signing. For more information, refer to theMicrosoft Learn Docs page about entitlements.
Also see thisMicrosoft Learn Docs page for more information.
TheVersionTracking API is still available in .NET MAUI the same as it is in Xamarin and Xamarin.Forms. However, the name of the store where values were stored and some other details have changed which causes the .NET MAUI version of your app to not being able to retrieve the previously saved version tracking information.
Note
For this API to work properly, you will have to make sure that the application identifier (or bundle identifier) is the same between your legacy Xamarin app and .NET MAUI app. This is needed so that the app gets installed in the same container on the operating system, which is needed to be able to read the version information that was stored previously.
Warning
Make sure that the app version of your .NET MAUI app ishigher than your legacy Xamarin application. Failing to do so might have unexpected results.
Also see thisMicrosoft Learn Docs page for more information.
This project could not have came to be without these projects and people, thank you! <3
The code in the plugin is mostly based on the original code inXamarin.Forms andXamarin.Essentials. It has been adapted for the Microsoft Learn Docs byDavid Britch.
About
A .NET MAUI plugin that provides helpers to make your transition from Xamarin.Forms to .NET MAUI easier
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Sponsor this project
Uh oh!
There was an error while loading.Please reload this page.
Packages0
Uh oh!
There was an error while loading.Please reload this page.