<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IOS on Bryan Avery</title><link>https://bryanavery.co.uk/categories/ios/</link><description>Recent content in IOS on Bryan Avery</description><generator>Hugo -- gohugo.io</generator><language>en-GB</language><copyright>© 2026 Bryan Avery.</copyright><lastBuildDate>Mon, 28 Nov 2016 09:15:00 +0000</lastBuildDate><atom:link href="https://bryanavery.co.uk/categories/ios/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction to IoC with Windsor</title><link>https://bryanavery.co.uk/introduction-to-ioc-with-windsor/</link><pubDate>Mon, 28 Nov 2016 09:15:00 +0000</pubDate><guid>https://bryanavery.co.uk/introduction-to-ioc-with-windsor/</guid><description>&lt;p&gt;I do love &lt;a href="https://bryanavery.co.uk/index.html%3Fp=158.html"&gt;&lt;strong&gt;&lt;span style="color: #4e4e4e;"&gt;dependency injection&lt;/span&gt;&lt;/strong&gt;&lt;/a&gt;, but many developers still seem to miss the point and the reason for having it. If you’re only using it on a small scale, you don’t really need any tools to use the technique. But once you’re used to this design technique, you’ll quickly start using it in many places of your code. If you do, it quickly becomes cumbersome to deal with the real instances of your runtime dependencies manually. This is where tools like Inversion Of Control (IoC) containers come in to play. There are a few solid containers available for the .NET world, and even Microsoft has released their &lt;a href="http://www.codeplex.com/unity" target="_blank"&gt;&lt;strong&gt;&lt;span style="color: #4e4e4e;"&gt;own container&lt;/span&gt;&lt;/strong&gt;&lt;/a&gt;. Basically, what the IoC container does for you, is take care of providing dependencies to components in a flexible and customizable way. It allows clients to remain completely oblivious to the dependencies of components they use. This makes it easy to change components without having to modify client code. Not to mention the fact that your components are a lot easier to test, since you can simply inject fake dependencies during your tests.&lt;/p&gt;</description></item></channel></rss>