maui-current-apis

Detect deprecated .NET MAUI APIs in project source code.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/seydakaratekeli/KamPay3 --skill maui-current-apis-seydakaratekeli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maui-current-apis
Source: https://github.com/seydakaratekeli/KamPay3/tree/main/KamPay/.github/skills/maui-current-apis%20-%20Kopyala
Command: npx skills add https://github.com/seydakaratekeli/KamPay3 --skill maui-current-apis-seydakaratekeli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents generation or use of deprecated, obsolete, or removed .NET MAUI APIs by analyzing project target frameworks and library versions to avoid broken builds and migration errors.

Core Features & Use Cases

  • Target framework detection: Reads .csproj TargetFramework/TargetFrameworks to determine the applicable .NET/MAUI version.
  • Library version analysis: Scans PackageReference entries to identify CommunityToolkit, MauiReactor, Blazor Hybrid, and other package versions that affect API availability.
  • Deprecated API mapping: Provides a curated table of common deprecated or removed APIs (for example ListView → CollectionView, Device.OpenUri → Launcher.OpenAsync) and recommended replacements across XAML, C#, Blazor Hybrid, and MauiReactor.
  • Generation guardrail: Enforces decision rules such as preferring Async methods, avoiding Xamarin. and Compatibility namespaces, and validating dispatcher and safe-area APIs during code generation or review.
  • Use case: Use this skill when reviewing or generating MAUI, Blazor Hybrid, or MauiReactor code to ensure compatibility with the project's target framework and package versions.

Quick Start

Ask the assistant to scan the project's .csproj and PackageReference entries and report deprecated MAUI APIs with recommended replacements.

Frequently Asked Questions about maui-current-apis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect deprecated .NET MAUI APIs in my project source code?

To detect deprecated .NET MAUI APIs, scan your project's .csproj TargetFramework and PackageReference entries to map obsolete symbols like ListView to CollectionView and recommend valid replacements. This prevents broken builds and migration errors across XAML, C#, Blazor Hybrid, and MauiReactor code.

What .NET MAUI APIs are deprecated and what should I use instead?

Common deprecated .NET MAUI APIs include ListView replaced by CollectionView and Device.OpenUri replaced by Launcher.OpenAsync. Mapping these obsolete symbols requires reading your .csproj TargetFramework and library versions to validate namespace, async, and compatibility rules.

Can I use this deprecated API detection for Blazor Hybrid and MauiReactor code reviews?

Yes, deprecated API detection applies to Blazor Hybrid and MauiReactor code reviews by scanning PackageReference entries to identify CommunityToolkit and other package versions affecting API availability. It enforces generation guardrails to ensure compatibility with your project's target framework.

How do I prevent obsolete .NET MAUI APIs during AI code generation and migration?

Prevent obsolete .NET MAUI APIs during code generation by applying decision rules that prefer Async methods, avoid Xamarin.* and Compatibility namespaces, and validate dispatcher and safe-area APIs. This enforces compatibility with the detected target framework and package versions.

Why does my .NET MAUI migration fail with obsolete API errors?

.NET MAUI migration fails with obsolete API errors when source code contains removed symbols incompatible with the target framework. Analyzing .csproj TargetFramework and PackageReference entries maps deprecated APIs to their replacements, enforcing async, namespace, and compatibility rules to resolve broken builds.