<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ninject on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ninject/</link>
    <description>Recent content in Ninject on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 04 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ninject/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>C# Dependency Injection Containers: Autofac vs Ninject vs Castle Windsor vs SimpleInjector vs Lamar Comparison 2026</title>
      <link>https://www.pistack.xyz/posts/2026-07-04-csharp-di-containers-autofac-ninject-castle-windsor-simpleinjector-lamar/</link>
      <pubDate>Sat, 04 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-04-csharp-di-containers-autofac-ninject-castle-windsor-simpleinjector-lamar/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Dependency Injection (DI) is the backbone of modern .NET application architecture. While Microsoft.Extensions.DependencyInjection (the built-in DI container) handles most basic scenarios adequately, enterprise applications quickly outgrow it — needing features like property injection, decorator/interceptor patterns, convention-based registration, named registrations, and advanced lifetime management. This is where third-party DI containers shine.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
