{"id":4329,"date":"2024-10-16T15:06:10","date_gmt":"2024-10-16T13:06:10","guid":{"rendered":"https:\/\/www.bayoomed.com\/?post_type=news&p=4329"},"modified":"2024-10-16T15:12:58","modified_gmt":"2024-10-16T13:12:58","slug":"from-xamarin-forms-to-net-maui","status":"publish","type":"news","link":"https:\/\/www.bayoomed.com\/en\/news\/from-xamarin-forms-to-net-maui\/","title":{"rendered":"From Xamarin.Forms to .NET MAUI"},"content":{"rendered":"

Challenges and learnings when migrating a Xamarin.Forms app to .NET MAUI<\/h2><\/h2><\/div>

Author: Simon Hirschel
\n<\/strong>Software Engineer at BAYOOMED<\/p>\n<\/div><\/div><\/div><\/div>

Co-author: Sebastian Wittor
\n<\/strong>Project Manager Medical Engineering at BAYOOMED<\/p>\n<\/div><\/div><\/div><\/div>

 <\/p>\n

With the release of .NET MAUI 6 in May 2022, we were faced with the question of whether a migration of the no longer supported Xamarin.Forms was necessary for our current project. There was also a deadline for iOS releases. From this point on, it would no longer be permitted to bring apps with outdated frameworks to the App Store. We now had to decide whether to rush blindly into the migration or look for alternative solutions. In the end, we decided to migrate our project to .NET MAUI 6 and later also to upgrade to .NET MAUI 8. You can read how we came to this decision in this blog article.<\/p>\n<\/div><\/div><\/div><\/div><\/div>

The first upgrade<\/h3><\/h3><\/div>

Microsoft provides a tool to update smaller Xamarin apps to MAUI. It replaces common usages and some settings with the new MAUI equivalents. Unfortunately, it doesn’t do much more than that and it still took a lot of work to get the app to compile without a lot of bugs. With MAUI, it is also recommended to switch from multiple projects for each platform to a single project with dedicated folders for each platform. We also needed to find replacements for some SOUPs that were essential to the inner workings of our app. These included Xamarin Essentials, which fortunately had a replacement in the MAUI Community Toolkit, and MvvmCross. As there was no equivalent replacement for MvvmCross, we had to remove and replace it. Since we were using MvvmCross for both views, view models, navigation and lifecycle events for the app, this was the biggest hurdle we had to overcome to get the app back up and running. Ultimately, this caused a lot of delays and required rewriting most of our parent views and view models to incorporate newly created events that were similar to the way MvvmCross handled them. In addition, we had to rework our entire navigation system to allow parameters to be passed and returned in the same way as before. Both of these changes were very time consuming and required a lot of testing and debugging before they worked in a way that allowed us to start making changes to the actual functionality of the app and its views.<\/p>\n<\/div><\/div><\/div><\/div><\/div>

Changed view<\/h3><\/h3><\/div>

One of the main issues was that controls in .NET MAUI do not work in the same way as in Xamarin.Forms. This difference means that some familiar UI elements require customization to work correctly in the new framework. In addition, the default values for padding, margins and other layout-related variables have changed. As a result, a significant amount of customization is required to make the views look similar to their previous versions. This requires customizing these properties for almost every single view in the application, which can be a time-consuming and painstaking task. Visual issues are also common during the migration process. Many views have inconsistencies that can only be resolved by further rewriting. Each view must be carefully reviewed and modified to fix these visual issues and ensure a consistent and polished look and feel across the application.<\/p>\n<\/div><\/div><\/div>

MvvmCross<\/h3><\/h3><\/div>

MvvmCross played a crucial role in our development process with Xamarin and saved us a lot of work. It was deeply integrated into our codebase and handled essential aspects such as app launch, app lifecycle and acted as a singleton provider. This extensive integration meant that MvvmCross was interwoven with almost every part of our application. However, the removal of MvvmCross during the migration to .NET MAUI caused numerous issues. We had to rewrite many lifecycle events for our view models as the previous implementation relied heavily on MvvmCross. We also had to develop our own navigation service manually as the built-in navigation provided by MvvmCross was no longer available. Almost all of our views had to be changed due to the absence of MvvmCross. This major overhaul was necessary to ensure that the views worked correctly and complied with the requirements of the new framework. Despite the challenges, overcoming these issues was essential for a successful migration to .NET MAUI and allowed us to maintain and improve the functionality of our application.<\/p>\n<\/div>

Bugs, bugs, bugs<\/h3><\/h3><\/div>
\n

When .NET MAUI was released as “production-ready” with .NET 6, we expected a smooth transition. However, the reality was very different. We encountered numerous errors that had a significant impact on our development process.<\/p>\n<\/div>\n

Firstly, some view elements did not work as expected. In addition, there were noticeable performance issues that made certain features, such as the carousel view, practically unusable. We also experienced several issues with MAUI running in Visual Studio 2022, especially after certain updates. Connection issues with MAUI on the Mac and deployment issues for iOS in the AppCenter further complicated the situation. Debugging also proved to be particularly difficult. The Visual Studio 2022 debugger often had issues with MAUI, making it difficult to identify and fix problems efficiently. Although fixes were promised, they were often delayed and only made available with the next .NET upgrade. These upgrades sometimes fixed existing issues but also introduced new ones, creating a cycle of troubleshooting and customization. Despite these challenges, we continued to work on the bugs and performance issues and endeavored to make the most of the new capabilities of .NET MAUI. Even though the journey was full of obstacles, each fix and workaround brought us closer to a stable and fully functional application.<\/p>\n<\/div>

Non-app-related challenges<\/h3><\/h3><\/div>

In addition to the technical hurdles, we faced several non-app-related challenges that complicated our migration to .NET MAUI. One of the main issues was the low developer capacity. With only a limited number of developers available, the workload became overwhelming and slowed down progress significantly. In addition, our focus was split due to other ongoing projects, so we could not fully concentrate on the migration process. This was exacerbated by the continuous release of updates and new features for Xamarin, which required additional time and effort to integrate and manage alongside the migration to .NET MAUI. These factors complicated the migration process overall, so we had to carefully allocate our time and priorities to make steady progress despite the constraints.<\/p>\n<\/div>

MAUI migration analysis before the migration attempt<\/h3><\/h3><\/div>

Before embarking on the migration to .NET MAUI, it is important to thoroughly analyze the potential challenges and requirements. Ask yourself the following questions to better estimate the migration effort:<\/p>\n<\/div>