Question 1

How do I choose a source generator for JSON serialization?

Accepted Answer

Compare options like JsonSrcGen for compile-time generation or MemoryPack for high-performance binary serialization. Check the README for links to their repos and benchmarks to assess speed and feature compatibility with your project.

Question 2

What are the main benefits of using source generators over reflection?

Accepted Answer

Source generators eliminate runtime reflection overhead, provide compile-time type safety, and can boost performance by generating code ahead of time. They also reduce boilerplate and enable AOT-friendly deployments.

Question 3

Source generators or traditional code gen tools: which is better?

Accepted Answer

Source generators are integrated into the Roslyn compiler, offering seamless compile-time updates without external tooling. Traditional tools like T4 templates are more flexible for complex workflows but lack native IDE support.

Question 4

How to create my own C# source generator?

Accepted Answer

Start with the Roslyn SDK samples and cookbook linked in the README. Use templates like DavidWengier's SourceGeneratorTemplate to set up the project, then implement code analysis and generation logic in your generator class.

Question 5

Can source generators be used with .NET Framework?

Accepted Answer

No, source generators require Roslyn compiler support introduced in .NET 5. For .NET Framework, consider traditional code generation methods or upgrade to a supported .NET version.

Question 6

How does Mapperly compare to AutoMapper?

Accepted Answer

Mapperly is a source generator that creates mapping code at compile-time, offering zero reflection and better performance than AutoMapper's runtime approach. However, AutoMapper has a larger ecosystem and more configuration options.

C# Source Generators

What is C# Source Generators?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions