Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
davidortinau avatar

Xamarin Android Migration

  • 22 installs
  • 163 repo stars
  • Updated July 6, 2026
  • davidortinau/maui-skills

Migrates Xamarin.Android native apps to .NET for Android, covering SDK-style project conversion, TFMs, MSBuild property changes, and manifest updates.

About

A workflow guide for migrating Xamarin.Android native apps to .NET for Android, covering SDK-style project conversion, target framework monikers, MSBuild property changes, AndroidManifest.xml updates and NuGet compatibility. A developer uses it when porting a Xamarin.Android app to modern .NET.

  • SDK-style project conversion and target framework monikers
  • AndroidManifest.xml updates and NuGet dependency compatibility

Xamarin Android Migration by the numbers

  • 22 all-time installs (skills.sh)
  • Ranked #735 of 1,039 Mobile Development skills by installs in the Skillselion catalog
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davidortinau/maui-skills --skill xamarin-android-migration

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs22
repo stars163
Last updatedJuly 6, 2026
Repositorydavidortinau/maui-skills

What it does

Migrates Xamarin.Android native apps to .NET for Android, covering SDK-style project conversion, TFMs, MSBuild property changes, and manifest updates.

Files

SKILL.mdMarkdownGitHub ↗

Xamarin.Android → .NET for Android Migration

For SDK-style project templates, MSBuild property tables, ABI conversion, namespace mappings, and CLI commands, see references/android-migration-api.md.

⚠️ Field-tested advice: Android migration is significantly harder than iOS.
Expect more UI bugs, OEM-specific rendering differences, and issues not
reproducible on emulators. Test on physical devices.

Migration Workflow

1. Create new .NET for Android project (dotnet new android) 2. Copy code and resources into the new project 3. Update MSBuild properties (see references/android-migration-api.md) 4. Update AndroidManifest.xml — remove <uses-sdk>, use csproj properties 5. Delete Resource.designer.cs (regenerated automatically) 6. Update NuGet dependencies 7. Migrate binding libraries (if applicable) 8. Replace Xamarin.Essentials with <UseMauiEssentials>true</UseMauiEssentials> 9. Handle encoding changes 10. Delete bin//obj/, build, test on physical devices

Strategy: Create a new project and copy code into it — don't edit the existing project file in place.

Critical Gotchas

⚠️ Remove <uses-sdk> from AndroidManifest.xml

<!-- ❌ Xamarin-style — causes build warnings/errors -->
<uses-sdk android:minSdkVersion="21" android:targetSdkVersion="33" />

<!-- ✅ Use MSBuild properties instead -->
<TargetFramework>net8.0-android</TargetFramework>
<SupportedOSPlatformVersion>21</SupportedOSPlatformVersion>

⚠️ Delete Resource.designer.cs

This file is auto-generated. Leftover copies from Xamarin cause duplicate symbol errors. Delete it — it will be regenerated.

⚠️ No .dll.config or .exe.config Support

.dll.config and <dllmap> are not supported in .NET Core. If your app uses System.Configuration.ConfigurationManager, migrate to appsettings.json or platform preferences.

⚠️ Essentials: Override Permissions in Every Activity

// ❌ Forgetting this → permissions silently fail
// ✅ Required in EVERY Activity that uses Essentials
public override void OnRequestPermissionsResult(
    int requestCode, string[] permissions, Permission[] grantResults)
{
    Platform.OnRequestPermissionsResult(requestCode, permissions, grantResults);
    base.OnRequestPermissionsResult(requestCode, permissions, grantResults);
}

⚠️ AndroidManifest.xml Location Changed

AndroidManifest.xml is now in the project root (not Properties/). The SDK-style project finds it there by default.

Platform-Specific Pitfalls

PitfallImpactMitigation
OEM rendering differencesUI bugs not visible on emulatorsTest on physical devices from multiple vendors
Shadow rendering varies by OEM/API levelInconsistent shadow appearanceImplement shadows in platform-specific handler code
Android Wear referencesNot supported in .NET for AndroidRemove Wear project references
MAndroidI18n removedEncoding errors at runtimeReplace with System.Text.Encoding.CodePages NuGet
AotAssemblies deprecatedBuild warningsUse RunAOTCompilation instead
jar2xml not supportedBinding library build failuresUse default class-parse parser
DebugType=full not supportedBuild errorsUse default portable

NuGet Compatibility Note

Android is unique: packages targeting monoandroid still work on .NET for Android. No recompilation needed for most Android-specific packages. This is NOT true for iOS/Mac.

If no compatible version exists: 1. Recompile with .NET TFMs (if you own it) 2. Look for a preview .NET version 3. Replace with a .NET-compatible alternative

API Currency Warning

If your migrated app will also adopt .NET MAUI controls (e.g., via UseMaui), check the maui-current-apis skill for deprecated MAUI APIs to avoid (ListView, Frame, Device.*, etc.).

Quick Checklist

1. ☐ Created new .NET for Android project (dotnet new android) 2. ☐ Set TargetFramework to net8.0-android (or later) 3. ☐ Set SupportedOSPlatformVersion for minimum SDK 4. ☐ Converted AndroidSupportedAbisRuntimeIdentifiers 5. ☐ Removed <uses-sdk> from AndroidManifest.xml 6. ☐ Copied source, resources, and project properties 7. ☐ Deleted Resource.designer.cs, bin/, obj/ 8. ☐ Updated NuGet dependencies 9. ☐ Added UseMauiEssentials + Platform.Init() if using Essentials 10. ☐ Overridden OnRequestPermissionsResult in every Activity 11. ☐ Replaced MAndroidI18n with System.Text.Encoding.CodePages 12. ☐ Verified AOT settings (RunAOTCompilation, not AotAssemblies) 13. ☐ Tested on physical Android device(s) from multiple vendors

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.