AgentStack
SKILL verified MIT Self-run

Xamarin Android Migration

skill-davidortinau-maui-skills-xamarin-android-migration · by davidortinau

>

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-davidortinau-maui-skills-xamarin-android-migration

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Xamarin Android Migration? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 ``, 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 true
  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 `` from AndroidManifest.xml


net8.0-android
21

⚠️ 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 ` 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

| Pitfall | Impact | Mitigation | |---------|--------|------------| | OEM rendering differences | UI bugs not visible on emulators | Test on physical devices from multiple vendors | | Shadow rendering varies by OEM/API level | Inconsistent shadow appearance | Implement shadows in platform-specific handler code | | Android Wear references | Not supported in .NET for Android | Remove Wear project references | | MAndroidI18n removed | Encoding errors at runtime | Replace with System.Text.Encoding.CodePages NuGet | | AotAssemblies deprecated | Build warnings | Use RunAOTCompilation instead | | jar2xml not supported | Binding library build failures | Use default class-parse parser | | DebugType=full not supported | Build errors | Use 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 `` 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.