Looks like BlogEngine.NET is it...
I've done some reading up (thanks to Noonie and Nick for the links) and from what I've been reading, BlogEngine.net is the way to go. I've not run it yet to try it out, but there's a few things mkaing it look like the correct path to follow:
- It's open. This means I can hack my own changes in (coz there's no way i'm doing ANY captcha without GAPTCHA :)
- It's simple. I'm busy lately. I don't want to spend hours figuring out the code base. The theming support looks hella-easy.
- It'll talk to SQL. Haven't exactly figured out how to turn this on yet, but I like the idea of a DB backend...I think.
- Dave Burke uses it. Back in the day when I was actively hacking my Community Server (read: this) blog, he and I were often (well...sometimes) trading coding hacks and tricks for running CS. If he's moved that way, it makes sense (Dave, get ready, expect me to harassing you again soon!). He's even written some scripts for migrating CS content to the new platform! (Thanks buddy).
- It does't have multiple-blog support - but that's not really a big deal. From what I can tell, it's just a matter of cloning the site over several applications (basically, run a new instance of BlogEngine for each virtual-directory (each user gets a new vdir). I think you can make them all share the same DB backend too, which would be good.
In the coming days (probably weeks) I'll be setting up a test BlogEngine.net site at home and having a play. Once I get GAPTCHA implemented and my old content migrated, then I'll start putting this blog to bed. Don't worry though, the main URL won't change....at least, I don't think it will. Probably the biggest issue is blog posts i've done that link to each other...with the new engine if the urls look different, then the links will 404...
Yes, I've still got a fair bit more reading to do to figure out all the issues...but so far, it's looking good.