<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>EF Core on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/ef-core/</link><description>Recent content in EF Core on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 13:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/ef-core/index.xml" rel="self" type="application/rss+xml"/><item><title>EF Core or Dapper? Two Ways to Talk to a Database from .NET</title><link>https://lab.artur-rios.tech/dotnet/ef-core-and-dapper/</link><pubDate>Wed, 21 Oct 2026 13:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/dotnet/ef-core-and-dapper/</guid><description>&lt;p&gt;Almost every .NET application that stores data ends up choosing how its C#&#10;code will talk to a relational database. Two names come up more than any&#10;other. &lt;strong&gt;Entity Framework Core&lt;/strong&gt; is Microsoft&amp;rsquo;s object-relational mapper: you&#10;describe your classes, and it writes the SQL, tracks what you change and&#10;evolves the schema. &lt;strong&gt;Dapper&lt;/strong&gt; is a small library from Stack Overflow: you&#10;write the SQL, and it turns the rows that come back into objects.&lt;/p&gt;</description></item></channel></rss>