Inversion of Control (IoC) and Dependency Injection (DI) are two related practices in software development which are known to lead to higher testability and maintainability of software products. While some people employ them daily in their work, many others still don’t know much about them, mostly because they require in the former a shift in the usual thinking process.

Within a project, classes will inevitably rely on each other. In some situations, this coupling can make code difficult to unit test or dynamically extend. A common solution is to this problem is to use a Dependency Injection Pattern. In this article we’ll look at how we can leverage the open-source Dependency Injection Framework called StructureMap, within The Code Wiki application.

The best way to learn how generics work is by looking at the problem they solve – which is rather straightforward. You use a generic whenever you have a piece of code which can be re-used by different types.

This article discusses the problem space generics address, how they are implemented, the benefits of the programming model, and unique innovations, such as constrains, generic methods and delegates, and generic inheritance. In addition it discusses how the .NET Framework utilizes generics

Optimising program code for maximum performance is often considered to be some sort of black art. Also, quite a number of programmers believe in micro-optimisations that rarely ever improve program execution time, but nearly always introduce subtle bugs or obfuscate the code, or both.

PInvoke.net is primarily a wiki, allowing developers to find, edit and add PInvoke* signatures, user-defined types, and any other information related to calling Win32 and other unmanaged APIs from managed code (written in languages such as C# or VB.NET).