xamarin-forms-migration

What problem does it solve?

Provides a practical, field-tested workflow to move existing Xamarin.Forms projects to .NET MAUI while avoiding common pitfalls that break layouts, renderers, effects, namespaces, and NuGet compatibility. It condenses project conversion steps, namespace mappings, renderer-to-handler migration patterns, layout behavior fixes, and platform-specific warnings into a single actionable guide for developers maintaining production apps.

Core Features & Use Cases

• Project conversion workflow: Create a new single-project MAUI app, copy cross-platform and platform code into Platforms/<platform>/, and iteratively update and build.
• Namespace and API mapping: Clear mappings from Xamarin.Forms and Xamarin.Essentials namespaces to Microsoft.Maui equivalents and guidance on deprecated .NET APIs.
• Renderer-to-handler and effects-to-behavior guidance: Patterns for using handler mappers and replacing effects with behaviors, plus warnings against shimmed renderers and compatibility packages.
• Layout and platform pitfalls: Explicit advice for MAUI default spacing changes, *AndExpand obsolescence, ScrollView sizing, Frame/Border differences, and Android-specific testing recommendations.
• Reference material: Integrated checklist and a detailed reference file for API and project file templates to use during migrations.

Quick Start

Use the xamarin-forms-migration skill to convert a Xamarin.Forms app to a .NET MAUI single-project by creating a new MAUI project, copying code into Platforms, updating Xamarin.* namespaces to Microsoft.Maui.*, migrating renderers to handlers and effects to behaviors, restoring explicit spacing and layout definitions, updating NuGet packages, and building iteratively to fix compiler errors.