DotNetKicks.com - Stories tagged with IoC

Making Unity work more like the others

Sat, 18 Apr 2009 00:16:14 GMT

I love MS Unity as an IoC container, it has some great features. Though I found it to function incorrectly at two points (it's not that the path chosen by the Unity team is incorrect, I just want/excpect it to act differently). The first thing that bothered me was the fact that Unity throws an exception when Resolve<T> is not able to resolve the given type: I'd prefer it to return null instead, hence most containers do that. The second, even more irritating point, was that ResolveAll<T> only returned the named instances/types instead of all registered types

Dependency injection in real world

Sun, 05 Apr 2009 09:02:59 GMT

Most of the blog posts I've seen present an ideal "perfect day" situation setup for writing the test which is not always the case in real world. In this kind of "not-so-perfect" situations, service locator based solution I've presented in that blog post allowed me to increase testability and introduce TDD into existing code bases and environments not so much interested in the TDD.

TDD Design Starter Kit - Dependency Inversion Principle

Sat, 21 Mar 2009 07:06:03 GMT

In the last episode of the TDD Design Starter Kit, I talked about the need to build cohesive classes, and make the relationships between classes loosely coupled. The specific benefit for TDD is to truly isolate the functionality of a class under the microscope of a unit test. But we've done all we can to isolate our classes, and we still have some interaction with dependencies.

Dependency Injection in ASP.NET MVC NerdDinner.com Application

Fri, 13 Mar 2009 15:52:39 GMT

Demonstrating how to apply Dependency Injection in the ASP.NET MVC NerdDinner.com application using Microsoft Unity Application Block.

TDD in SharePoint - Introduction to common vocabulary

Wed, 11 Mar 2009 05:30:58 GMT

This post is part of a series on Test Driven Development - Using Dependency Injection. There are a number of terms that you are likely to hear very early on in your journey to Test Driven Development, these terms generally refer to specific patterns of coding that have developed to support particular problems. You should be familiar with terms like Singleton and Factory which are used as a common vocabulary and help developers to communicate their design. In order to complete the refactoring of our project we will introduce some new terms Loosely Coupled, Dependency Inversion, Dependency Injection and Inversion of Control to help us describe the changes and the reasoning behind them.

IoC - 'A Simple Example' with Castle

Fri, 13 Feb 2009 00:52:27 GMT

A simple, easy to follow example of implementing IoC using Castle Windsor

IoC libraries compared

Fri, 09 Jan 2009 01:01:06 GMT

A comparison of how to initialize various IoC libraries. Including AutoFac, Ninject, Spring.Net, StructureMap, Unity, and Windsor.

Dependency injection with Castle Windsor: Video

Wed, 12 Nov 2008 01:42:07 GMT

Here's the video from the talk on dependency injection with Castle Windsor that Mike Hadlow and Gojko Adzic did last month at Skills Matter.

Spring.NET 1.2.0 Released

Tue, 11 Nov 2008 01:00:52 GMT

The Spring.Net framework version 1.2.0 has been released today and it features among others WCF and MSMQ integration as well as 100 bug fixes and enhancements since the 1.1.2 release.

Proof of Concept: a simple DI solution for ASP.NET WebForms

Mon, 27 Oct 2008 22:39:44 GMT

Building a simple, reusable Http Module that gives folks DI scoped to the Application, Session, and Request. List of requirements (scaled to just the application level) that looked sort of like this: Create a DI container for the application Create a way to get to the container ( we choose an extension method on the Application class) Allow a way to configure the container Allow DI to work for pages Allow DI to work for user controls Allow DI to work for master pages Allow DI to work for ASMX web services Allow the above functionality in a simple and self contained way

Converting the CWAB to Unity - Using the UnityCompositionContainer

Mon, 27 Oct 2008 22:37:40 GMT

This is the sixth post in a series. The other post include: Converting the Composite Web Application Block to Unity - Intro. Converting the Composite Web Application Block to Unity - Adding an ICompositionContainer Converting the Composite Web Application Block to Unity - Clean Up ICompositionContainer Converting the Composite Web Application Block to Unity - Ummmm...Oooops. Converting the Composite Web Application Block to Unity - Actually Adding Unity

ASP.NET MVC Tip: Dependency Injection with Unity Application Block

Sat, 25 Oct 2008 12:02:39 GMT

In this post, I demonstrate how you can use dependency injection pattern using Microsoft's Unity Application Block (Unity). If you want to develop an ASP.NET MVC application fully with Microsoft stack, you can use Unity Application Block to perform dependency injection.

Insidious Dependencies

Thu, 23 Oct 2008 01:46:02 GMT

Many dependencies in code are obvious, such as relying on a particular framework or database implementation. Others can easily be overlooked. This article exposes some of the more insidious dependencies that commonly exist within applications which may be overlooked as such.

Envrionment Validation and Windsor Extensibility

Fri, 17 Oct 2008 09:01:49 GMT

Adding envrionment validations to Windosr: "StructureMap does really well is the ability to ask the container to perform envrionment validations, to make sure that the envrionment is ready for us"

Common IoC denominator for Autofac, Castle and Unity .NET Containers

Sun, 12 Oct 2008 15:36:18 GMT

What's the common denominator for the Autofac, Castle, Unity and other popular .NET containers? Some think, that it is the CommonServiceLocator - an interface that will allow library developers to abstract from the specific Container or Service Locator implementation.

What is this Managed Extensibility Framework thing all about ?

Fri, 26 Sep 2008 17:31:12 GMT

Another IoC Container From Microsoft ? Add-in Framework ? What the heck is it ? Sidar tries to answer.

BFG: DSL configuration syntax for Autofac IoC Container

Tue, 23 Sep 2008 03:32:57 GMT

This might be interesting for people that use popular IoC container for .NET - Autofac. Now it is possible to configure this container with the custom DSL syntax that is more flexible and efficient than plain XML configuration.

Implementing Exception Handling Application Block with Photon.NET

Thu, 18 Sep 2008 11:36:53 GMT

Let's implement lightweight EntLib Exception Handling with the Autofac IoC and Boo DSL

Comparing .NET DI (IoC) Frameworks, Part 2

Tue, 09 Sep 2008 16:46:03 GMT

A second part of popular IoC frameworks comparison.

Spoiled with Dependency Injection

Tue, 09 Sep 2008 03:45:13 GMT

This post could be interpreted as a starting point to get links and a few warm words to the choice of DI container available out there

Unity - Dependency Injection and Inversion of Control Container

Tue, 09 Sep 2008 22:01:14 GMT

Dependency injection is a programming technique to reduce component coupling. Dependency injection is also commonly known as "inversion of control" or IoC or sometimes as The Hollywood Principle - "Don't call us, we'll call you". The goal of dependency injection is to separate the concerns of how a dependency is obtained from the core concerns of a boundary. This improves reusability by enabling components to be supplied with dependencies which may vary depending on context.

Mini IOC and Static gateway logging - Andrew Stopford's Weblog

Thu, 04 Sep 2008 10:54:42 GMT

Quickly add logging using "static gateway logging example" and a mini IoC.

Comparing .NET DI (IoC) Frameworks, Part 1

Wed, 20 Aug 2008 05:18:44 GMT

A first part of feature comparison between the most popular DI (IoC) Frameworks: Castle, Unity, Autofac, Ninject, StructureMap and Spring.Net.

Logging With Ninject

Sat, 21 Jun 2008 22:32:43 GMT

Simple logging with Ninject.Integration.Log4net and AutoWiring

SubSonic: Writing Decoupled, Testable Code With SubSonic 2.1

Thu, 19 Jun 2008 05:31:56 GMT

I've heard/read rumblings over the last few months that "SubSonic is tightly coupled" and therefore you have to "drag it around" with you in your project. I can see why people might think this - ActiveRecord is not the most testable thing in the world :). I've really tried to push SubSonic into the TDD realm and thought it might be a good idea to show how you can structure up a highly testable, decoupled application using SubSonic as your Data Access tool.