
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Remigiusz Zalewski | Become a Better .NET and AI Engineer</title>
      <link>https://remigiuszzalewski.com/blog</link>
      <description>Practical C#, .NET, ASP.NET Core and EF Core tutorials with code examples and video walkthroughs, from authentication and databases to Azure deployment and AI tools.</description>
      <language>en-us</language>
      <managingEditor>remigiuszzalewski.business@gmail.com (Remigiusz Zalewski)</managingEditor>
      <webMaster>remigiuszzalewski.business@gmail.com (Remigiusz Zalewski)</webMaster>
      <lastBuildDate>Fri, 05 Apr 2024 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://remigiuszzalewski.com/tags/relationships/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://remigiuszzalewski.com/blog/ef-core-relationships-one-to-one-one-to-many-many-to-many</guid>
    <title>Mastering EF Core Relationships: One-to-One, One-to-Many, and Many-to-Many in .NET</title>
    <link>https://remigiuszzalewski.com/blog/ef-core-relationships-one-to-one-one-to-many-many-to-many</link>
    <description>Every EF Core relationship bug traces back to a misunderstood foreign key or a missing configuration. One-to-one, one-to-many, and many-to-many mapped explicitly with the Fluent API, and where EF Core&#39;s conventions quietly get it wrong.</description>
    <pubDate>Fri, 05 Apr 2024 00:00:00 GMT</pubDate>
    <author>remigiuszzalewski.business@gmail.com (Remigiusz Zalewski)</author>
    <category>.net</category><category>csharp</category><category>entity-framework</category><category>efcore</category><category>relationships</category><category>fluent-api</category>
  </item>

    </channel>
  </rss>
