Handling multiple implementations of an interface with Dependency Injection in .Net Core

When you have an interface with multiple implementations and you don't want to use a 3rd party DI framework, you'll need to work around some limitations of the 'native' DI implementation in .Net Core.

Swashbuckle custom ordering of controllers

By default, Swagger (or rather: Swashbuckle) orders the documentation of controllers by controllername. So if you have a FooController, BarController and BazController they will be ordered as Bar, Baz, Foo in the swagger UI. Let's change that.

Configure your Windows Remote Desktop (RDP) to use TLS with a StartSSL certificate

I wanted to use TLS with non-self-signed certificates for RDP connections to my workstation at home and so I set out to make it happen. Since I don't have a domain with Active Directory (anymore...) the 'usual' methods found on the web don't quite apply. Here's a simple, step-by-step, guide on how to use StartSSL certificates to secure your RDP connection. This should also work fine with certificates from other CA's; step 2 and 3 (obtaining the .crt file)  can/will be different but other than that you should be fine.

Do you really want "bank grade" security in your SSL? Dutch edition

Inspired by Do you really want "bank grade" security in your SSL? Here’s how Aussie banks fare found on /r/programming I present to you the "Dutch edition". The author used Qualys SSL Labs' SSL test to determine how good banks' SSL implementations really are.

MongoVue GridFS bug

I have been a MongoVUE user for some time and have always been quite happy with it. I had a bug or problem a few years ago (can't remember what exactly) and was quite astonished that their site doesn't feature a "support" section. All you can do is click "contact us" and fill in some crappy e-mail form. Back then, if I recall correctly, it must've done the job because the bug has been fixed (I guess).

Get rid of that annoying clientsfromhell.net popup!

I love a chuckle now and then and Clients From Hell provides just that. It has done so for a long time. But for some time now it has been nagging me (and everyone) with some stupid popup that you can close but, at best, for 30 days before it starts nagging again.

A TimerWheel implementation in C# with flexible rescheduling

Recently we started a project that, among a lot of other stuff, required many objects to be scheduled (and rescheduled) for processing. Each of these objects could, potentially, require it's own interval; for example object A could be required to process each 10 seconds, object B could need an interval of 3600 seconds and object C could need to be processed each second. As long as there's a handful of objects, instantiating a timer for each object would be an option. But since our collection could grow to contain more than thousands of objects I felt that having a timer hanging around for each of those objects wasn't the best idea ever. This was just a gut-feel until I later stumbled upon a blog-post from one of my all-time favorite bloggers Raymond Chen. Although, apparently, it's okay to have many timers lying around I felt there had to be a more efficient way to solve my problem.