Switching to BlogEngine.NET

You may have noticed that things look a little different around here.  I finally got fed up with the themes in dasBlog.  The CSS in many of them was just plain bad, with fields overlapping each other and content scrolling off the screen when it shouldn’t.  I know theming seems like kind of a small thing to switch blog engines over, but really, the look and feel of your website can say a lot about your professionalism, so I felt it was worth it to find something I was happy with.

I looked at several different engines before deciding on BlogEngine.NET.  WordPress is very popular, and can be made to look very nice, but my site is hosted on Windows, and from what I read WordPress needs to run on Linux.  I also looked at GraffitiCMS, which was very nice, and much easier to set up than other CMSes I’ve worked with before.  Although blogging is possible with it, it seems a little more general-purpose than I was looking for. 

I watched a how-to video on setting up BlogEngine.NET, and looked fairly lightweight and easy to set up. I also liked the variety of acceptably clean-looking themes.  The clincher for me though, was this post by Merill Fernando talking about exporting his dasBlog setup to blogML and being able to import it right into BlogEngine.NET.  He even wrote a nice little GUI front-end to handle the export from dasBlog.  The whole process was pretty painless, and I didn’t lose my old posts.

I also picked up the nice DarkBlog theme created by Ruslan Tur, but changed the stylesheets to use blue text instead of green.  I’m pretty happy with the result, and I’d recommend BlogEngine.NET to anyone looking for an engine.  Your thoughts on the change are welcome!

One thought on “Switching to BlogEngine.NET

  1. Joe

    Brian! Hey man, just seeing what’s up? How are things in Shreveport?

    I’ve been on vacation and just got back, and noticed as I browsed over Hanselman’s posts, that you were on there, so I thought I would drop by and drop you a line. Just saying “Hey!”

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *