<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nhibernate on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/nhibernate/</link>
    <description>Recent content in Nhibernate on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 06 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/nhibernate/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted C# ORM Libraries Compared: Entity Framework Core vs Dapper vs NHibernate in 2026</title>
      <link>https://www.pistack.xyz/posts/2026-07-06-csharp-orm-libraries-entity-framework-core-dapper-nhibernate/</link>
      <pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-06-csharp-orm-libraries-entity-framework-core-dapper-nhibernate/</guid>
      <description>&lt;p&gt;Choosing the right Object-Relational Mapper (ORM) is one of the most consequential decisions in any .NET project. The ORM sits at the boundary between your application code and the database, influencing performance, maintainability, and development velocity. In the .NET ecosystem, three ORMs have stood the test of time: &lt;strong&gt;Entity Framework Core&lt;/strong&gt; (Microsoft&amp;rsquo;s flagship), &lt;strong&gt;Dapper&lt;/strong&gt; (the lightweight speed champion), and &lt;strong&gt;NHibernate&lt;/strong&gt; (the enterprise-grade veteran).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
