Updated: new version here! I have compiled two cheat sheets about clean code (the ones mentioned in my post about Code Quality!). The first covers clean code – code that is easy readable and keeps changeable. The second is about Test Driven Development. Both cheat sheets list principles, patterns, practices and smells. You can download them here – Clean Code Cheat Sheet V1.3, Clean TDD Cheat Sheet V1.2. Take a look! I’d like to read your feedback in the comments section… (just an...
Dependency Injection with Windows Workflow Foundation 4 advanced
In this follow up post I try to tackle the more advanced stuff which is possible with the new ninject extension for Windows Workflow Foundation. The goal is to show the following topics:
Hooking into the injection chain
Possible side effects
Changing the extensions behavior
Download the extension
Dependency Injection with Windows Workflow Foundation 4 an answer
In my last post I raised the following questions:
How do you inject dependencies into activities without having to declare the dependencies as input arguments?
How do you build up extensions using DI mechanism?
How do you unit test components which host workflow applications or workflow invokers without actually invoking a real workflow?
In this follow up post I try to answer these questions.
How to use the additional Ninject Scopes of NamedScope
The Named Scope extension adds the three additional Scopes InCallScope, InNamedScope and InParentScope to Ninject. In this Blogpost I want to explain how they are used. Some parts of this post expect that you have a basic knowledge about the Context Preservation extension. Consider reading my blog post about the Context Preservation Extension before reading this one.
Ninject.Extension.ContextPreservation explained
In this blog post I explain how the Context Preservation extension works and for what it is used.
Ninject and extensions 2.2 RC2 available for download
I gladly announce that there is another Release Candidate vor Ninject 2.2 with minor changes available for download at Github.
Dependency Injection with Windows Workflow Foundation 4 Introduction
Windows Workflow Foundation 4 offers a comprehensive set of tools to design, create and host your own workflows in your application. Normally when working with WF4 the only way to get your external dependencies into the workflow is by passing the dependencies as arguments to the workflow host such as WorkflowApplication, WorkflowInvoker or WorkflowServiceHost.
Official Ninject MVC extension gets support for MVC3
MVC3 added support for Dependency Injection frameworks. To take advantage of these features I did a completely new implementation of the Ninject.Web.Mvc extension. Unlike other existing MVC3 implementations for Ninject, this extension goes further than just adding a IDependencyResolver for Ninject. It has tightly Ninject integrated support for various things such as Filters and Validators.
This post assumes that you have a basic knowledge about MVC, Ninject and Dependency Injection in general.
MockOf: How neat is that?
Are you tired of using the object property in MOQ?
Are you tired of declaring a huge amount of local variables to declare complex hierarchies?
…
Have a look at the new Mock.Of<T> feature in MOQ! Let’s see an example.
Dynamic Proxy for WCF with Castle DynamicProxy
In a project I’m currently working we are using Windows Communication Foundation with automatically generated client proxies from interfaces in a shared library. This is the ideal approach for us because we are under control of the service provider and service consumer and when developing our stories for the application we can quickly introduce new service providers which then are automatically available at the client side. So far so good. But when using Windows Communication Foundation...