<?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>Ioc on Benny Simmonds</title>
    <link>https://www.bencode.io/tags/ioc/</link>
    <description>Recent content in Ioc on Benny Simmonds</description>
    <generator>Hugo -- 0.149.1</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 22 Mar 2012 07:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.bencode.io/tags/ioc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Autofac Your WCF</title>
      <link>https://www.bencode.io/posts/2012-03-22-autofac-wcf/</link>
      <pubDate>Thu, 22 Mar 2012 07:00:00 +0000</pubDate>
      <guid>https://www.bencode.io/posts/2012-03-22-autofac-wcf/</guid>
      <description>&lt;p&gt;Autofac (a .NET IoC container) makes .NET code better. Simple. Controlling the way software interacts with it&amp;rsquo;s components (dependencies) is one powerful way to the increase its &amp;ldquo;bendability&amp;rdquo;. Bendability meaning how well a chunk of software is able to cope with change (this is inevitable). WCF&amp;rsquo;s unique object model (bindings, endpoints, behaviors, contracts, etc) can make doing IoC more of a challenge, however Autofac&amp;rsquo;s native WCF integration comes to the rescue.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
