Have you wondered why I haven’t posted in a while? Well, I was away for a couple of weeks on vacation, and plenty busy before that, so there has been little time to sit down and write some meaningful content :-).

Hopefully now that I’m back I should be able to start posting again more regularly.


While on the topic of blogging; I’ve been toying with the idea of migrating my website for a while to a different platform. Right now it’s a rag-tag combination of dasBlog, some custom (and old!) ASP.NET code and a bunch of HTML files, and I’d like to move it all into something simpler with some basic CMS capabilities.

I’m also, quite honestly, fed up with dasBlog. It was a fine tool and pretty good for it’s time, but it has started showing it’s age already, and it has a number of really annoying issues.

I’m not particularly interested in other .NET engines at this time, and have little desire to have to get up (and pay for) SQL Server just to run this site. I’ve been contemplating getting a [linux-based] Virtual Private Server for several reasons, and this is a good chance to move away from dasBlog into something that runs better in that environment.

What I have not decided on yet is what tool to use. So far, looks like it might be either Movable Type (which I used to run this blog on win32 for years), or Wordpress. I already have some ruby code that I can use to import all my existing dasBlog content into either tool, so at least that’s mostly taken care of.

Movable Type

MT has improved quite a bit since the last time I used it, and getting a copy up and running was fairly easy. It still has some really nice features, one of which is that getting all my content up and setting up the appropriate redirects and rewrites to keep existing links valid turned out to be pretty easy because of how archiving works in MT.

It does have a bunch of downsides as well, one of which is that MT is still mostly geared towards static publishing (i.e. HTML is generated and written to files served statically), which can be really annoying when you need to make site-wide changes. Though MT currently supports dynamic publishing through a PHP script and sort of works, it doesn’t support a bunch of stuff in this mode, and a lot of plugins simply don’t support this at all.

Also, the lack of built-in paging for archives for MT is, well, disappointing to say the least!


Wordpress is definitely polished and very easy to setup. I originally toyed with importing my dasBlog content directly into the WP database, but it’s a drag, and ended up importing it from the same output I used for importing in MT, which worked fine.

I did need to use the raw-html plugin to force Wordpress to avoid messing up all my code samples. The plugin works nicely, fortunately, because this “feature” makes WP pretty much unusable for me.

Unfortunately, adding all the redirects for imported content to keep existing links working is a lot more difficult with WP. I’m still not sure the best way to go about it, but it will likely involve extracting some info from the WP database and combining it with some output from the conversion process to add some sort of map-based redirection scheme. Ugly, to say the least.

If anyone has any ideas, or can suggest another tool (something that hopefully supports Windows Live Writer), please do let me know!

Tomas Restrepo

Software developer located in Colombia. Sr. PFE at Microsoft.