OWIN (Open Web Interface for .NET) is an open source initiative to define the specification of an interface between
.NET web applications and servers; it aims to enable web applications to become decoupled from IIS by removing the
dependency on the System.Web assembly. With OWIN, you can write “middleware” to hook into the request pipeline which
is what this article will be focusing on.
Ever since I started blogging back in 2009 I’ve always run it on Wordpress. I always found Wordpress to be okay but was never
fully satisifed with it. It felt a bit like overkill for what I needed and the writing experience was forever frustrating me.
Recently I decided to look into alternatives that would be much lighter weight and simpler to manage than Wordpress; I settled
Sometimes when you first start working on an existing project you come across some code that’s a bit quirky or weird. This is normally due to personal preferences or misunderstandings but whatever the reason, you can live with it - it’s not that bad. Other times you just come across code that makes you quietly weep as you resign yourself to spending the next few months in this hell; a .NET project which uses the “Static Everything” (anti-) pattern is one of those times (is this actually a pattern? I don’t know but I’ll be calling it a pattern throughout this post). The Static Everything pattern is when core operations and business logic in a code base is mostly made up of static classes with static utility methods scattered everywhere; some of which may even have static “state” (!!). This is typically accompanied by simple domain/model classes that simply define properties for an entity.