DEV Community

Cover image for Xamarin, I Hate U

Posted on

Xamarin, I Hate U

As a Xamarin and .NET MAUI user, I am actually very happy with the existence of this framework because with one language, we can write both the backend and mobile applications (using ASP.NET Core and Xamarin).


I am a programmer who deals with .NET, Xamarin, and SQL Server on a daily basis. I work for an enterprise where introducing a new technology requires extensive and costly studies, unlike startups that can easily propose relevant technologies for the problems they are addressing.

Main Problem

I need to migrate from Xamarin to .NET MAUI because Xamarin will be out of support in 2024. You can find more information about it here:

Performing this migration is not as simple as it may seem. First and foremost, we need to merge the Xamarin.Android and Xamarin.iOS sources into a single project before we can combine them into .NET MAUI. Some of you may wonder, "Why were the Android and iOS projects separated in the first place?" The answer is that at that time, we lacked sufficient proficiency in Xamarin. Therefore, we chose to keep the source code separate to minimize the occurrence of errors.

Image description

You might be thinking now, why don't we just merge the two Xamarin projects first and then migrate to .NET MAUI? Well, that's exactly what we thought, but in reality, it's still challenging. We need to set up the .NET MAUI project first, but every time we try to set it up for the iOS platform, it keeps switching to .NET 7, even though we initially set it up for .NET 6.

Image description

In the end, all of this is in vain. It has been a week, and we are still stuck in the project setup process. It feels like we are just waiting for a time bomb to explode when the boss asks, "Why can't we publish our app?"

Top comments (0)