Author Archive

I recently updated my home page to include summary of the latest posts for this blog. Here is a screen shot of the summary section: I am using dasBlog as my blog engine and I originally approached

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,

I am working on a project that once again requires a slide show on the page. Previously, I posted on a more complex slide show that was configurable. This time everything is much simpler. I have a

I have a number of third party libraries that I use in my applications. I also have a number of utility type assemblies that I have created and re-use in many applications. In this post, I will

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

In this post, I will explore installing and configuring Hudson as a continuous integration server for .NET projects. Why Hudson? This is good question. I know other CI servers exist, however, Hudson happens to already be an

One step in setting up your continuous integration environment is getting your tests to run via a command line. My development environment is Visual Studio and I am using the Microsoft testing framework. I did not imagine

As some of you know may know, the Mono Project allows your .NET Framework applications to run cross platform. Mono’s .NET implementation is based on the ECMA standards for C# and the Common Language Infrastructure. It is