rm-guide-dotnet9

Evaluates .NET 9 API adoption for targeted C# code paths.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill rm-guide-dotnet9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rm-guide-dotnet9
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/redmuffin-standards/rm-guide-dotnet9
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill rm-guide-dotnet9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers decide when advancing to .NET 9 APIs improves performance or maintainability versus sticking with current runtime practices.

Core Features & Use Cases

  • Runtime guidance: Recommends preferring current .NET 9 APIs when they simplify code or boost performance.
  • Performance focus: Encourages using modern collections, spans, and cached JsonSerializerOptions in hotspots.
  • Practical review: Ideal when auditing performance-sensitive C# code for runtime improvements or API updates.

Quick Start

Evaluate the target code path and request advice on applying CountBy, JsonSerializerOptions caching, and span-based APIs before adopting .NET 9.

Frequently Asked Questions about rm-guide-dotnet9

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

FAQPage Schema
What .NET 9 APIs improve performance in C# hotspots?

For .NET 9 runtime modernization, adopting LINQ CountBy/AggregateBy, cached JsonSerializerOptions, and span-based APIs can improve performance and simplify code in targeted hotspots.

How do I evaluate whether to adopt .NET 9 APIs for existing code paths?

Evaluate .NET 9 API adoption by auditing performance-sensitive C# code paths to determine if modern collections, spans, or cached JsonSerializerOptions offer measurable improvements over current runtime practices.

When should I use LINQ CountBy and AggregateBy in .NET 9?

Use LINQ CountBy and AggregateBy during .NET 9 runtime modernization when they simplify code or boost performance in targeted hotspots, preferring them over current collection practices.

Does .NET 9 change how I should handle JSON serialization options?

Yes, .NET 9 performance guidance recommends caching JsonSerializerOptions in hotspots rather than recreating them, improving both runtime performance and maintainability.

What are the limitations of upgrading to .NET 9 span-based APIs?

Limitations of .NET 9 span-based APIs involve assessing whether they genuinely simplify code or boost performance in specific hotspots versus sticking with current runtime practices.

Can I use this guidance for auditing maintainability in C# projects?

Yes, this guidance is ideal when auditing performance-sensitive C# code for runtime improvements, helping decide if .NET 9 API updates enhance maintainability or performance.