This post does not pertain to the most recent (shortly after the release of this post) versions of Ninject. Ninject now handles the deactivation of all objects bound ‘InRequestScope’. Recently a discussion with a reader led to
I have deployed the Truck Tracker application to here for now: https://bobcravens.com/trucktracker/ The application is built using the following technologies: ASP.NET MVC Google Maps API v.3 jQuery DotNetOpenAuth MySQL NHibernate Ninject The intent of the application is
In a previous post we built a MySQL database and a data access layer via a repository pattern implemented using Fluent LINQT to NHibernate. We also wired up this repository in our ASP.NET MVC application using Ninject.
This is a continuation of a “truck tracker” sample application that leverages NHibernate as an object relational mapper (ORM). I previously created the entities, defined a repository interface, and implemented the repository using NHibernate. During this blog
I am really enjoying Ninject as an IOC container. If you want to get started with Ninject check out my previous posts: Ninject – Getting Started, Resources, Basic Binding Ninject – Life Cycle Management or Scoping Recently,
Previously we discussed getting started with Ninject and dependency injection in general. In the getting started post, we introduced a fictitious example application. This application defined concrete implementation for the following interfaces: IFileSystem – Abstraction of file
This post will cover the information needed to get started with Ninject. By the end of this post, you will be able to use Ninject in your application as a dependency injector. Here is a description from
In future posts, I plan on diving into Ninject 2. As I was writing that post, I found myself covering a lot of background material on dependency injection (DI) and inversion of control (IOC) containers. This is