<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Source-Generation on .NET wat we zoeken</title><link>https://blog.netwatwezoeken.nl/tags/source-generation/</link><description>Recent content in Source-Generation on .NET wat we zoeken</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 21 Feb 2022 12:45:04 +0200</lastBuildDate><atom:link href="https://blog.netwatwezoeken.nl/tags/source-generation/index.xml" rel="self" type="application/rss+xml"/><item><title>Source generation in System.Text.Json, should I care?</title><link>https://blog.netwatwezoeken.nl/posts/source-generation-in-system-text/</link><pubDate>Mon, 21 Feb 2022 12:45:04 +0200</pubDate><guid>https://blog.netwatwezoeken.nl/posts/source-generation-in-system-text/</guid><description>&lt;p&gt;With the release of .NET 6 also came the option to use source generation in System.Text.Json. In short this means that instead of runtime reflection some of the work is now done compile time. This makes it more efficient. But how much? And should I care?
Just measure it. I made a small project that you can use and adjust to measure the difference for your specific case. Let the results help you decide what&amp;rsquo;s best for your application.&lt;/p&gt;</description></item></channel></rss>