We received the following question about building Ninject: I’ve downloaded the source files for both context extensions and namedscopes (Ninject) and have followed the instructions in "how to build.txt" exactly, but I cannot get either NAnt script to build. I keep getting an error from git saying "get-git-revision: [exec] fatal: Not a git repository (or any of the parent directories): .git BUILD FAILED – 0 non-fatal error(s), 1 warning(s)" what gives? what do I...
I just released Ninject 18.104.22.168 and Ninject.MVC3 22.214.171.124. Both are bugfix releases. In this Blogpost I’ll explain if you have to update and what changes you need to do in case you are using th NuGet version of Ninject.MVC3.
With Ninject.MVC3 126.96.36.199 available from NuGet Ninject.MVC3 and Ninject.Web.MVC3 got merged into one project providing the advantage or both.
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
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.
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.
In this blog post I explain how the Context Preservation extension works and for what it is used.
I gladly announce that there is another Release Candidate vor Ninject 2.2 with minor changes available for download at Github.
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.
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.