What is the 'polyfill-first' approach in .NET?

It is a strategy that prioritizes using source generators like PolySharp to enable modern C# syntax on older frameworks before resorting to conditional compilation (#if) blocks.

When should I use conditional compilation instead of a polyfill?

You should use #if blocks when there is a runtime behavior difference that cannot be fixed at compile-time, or when dealing with platform-specific APIs like Windows Registry.

Can I use modern C# 12 features on .NET Standard 2.0?

Yes, by using this skill's guidance on PolySharp, you can use features like 'init' properties and 'required' modifiers even when targeting older runtimes.

How does this skill interact with other .NET skills?

It consumes version data from the dotnet-version-detection skill and provides the architectural foundation for the dotnet-version-upgrade skill.

.NET Multi-Targeting Strategy

Name: .NET Multi-Targeting Strategy
Author: rudironsoni

byrudironsoni

0•

Developer Tools

Guides developers through complex .NET multi-targeting scenarios using a polyfill-first approach to maximize code compatibility and modern syntax usage.

The dotnet-multi-targeting skill provides a comprehensive framework for managing multiple Target Framework Monikers (TFMs) within .NET applications. It advocates for a 'polyfill-first' strategy, utilizing tools like PolySharp and SimonCropp/Polyfill to backport modern C# language features and BCL APIs to older runtimes without adding runtime dependencies. By providing a clear decision matrix, it helps developers choose between polyfills, conditional compilation, and adapter patterns, ensuring that cross-platform libraries and legacy migrations remain maintainable and performant.

Key Features

01Implementation patterns for SimonCropp/Polyfill for BCL API backporting

02Polyfill-first strategy for backporting modern C# features to older TFMs

030 GitHub stars

04Guidance on using PolySharp for compiler-synthesized attribute stubs

05Decision matrix for choosing between PolySharp, BCL polyfills, and #if blocks

06Structured TFM-based preprocessor symbol management and API validation

Use Cases

01Using modern C# 11+ features like 'required' members on older .NET Standard 2.0 targets

02Validating API compatibility across multiple target frameworks during library development

03Developing NuGet packages that need to support both legacy .NET Framework and modern .NET

Key Features

01Implementation patterns for SimonCropp/Polyfill for BCL API backporting

02Polyfill-first strategy for backporting modern C# features to older TFMs

030 GitHub stars

04Guidance on using PolySharp for compiler-synthesized attribute stubs

05Decision matrix for choosing between PolySharp, BCL polyfills, and #if blocks

06Structured TFM-based preprocessor symbol management and API validation

Use Cases

01Using modern C# 11+ features like 'required' members on older .NET Standard 2.0 targets

02Validating API compatibility across multiple target frameworks during library development

03Developing NuGet packages that need to support both legacy .NET Framework and modern .NET