DasBlog vs WordPress - Ease of Installation
I recently switched hosting providers from HostMySite to WebHostASP. My new hosting provider is cheaper and offers me more features.
Anyway, I also decided to change my blogging engine (my earlier blog was using Wordpress). I wanted to move over to an asp.net based blog. I am frequent listener of Hanselminutes pod cast, and Scott Hansleman uses DasBlog for his blog; so, I decided to try it out (being a fan and all that)…
Now I tried a couple of times to deploy DasBlog onto my webhost but each time I ended up with all kinds of errors (after following the instructions carefully from the forums as well). I needed something to work out-of-the-box and even though DasBlog looks very feature rich, I couldn’t get it to work right away. (i should also mention that i was only able to give it about 1-2 hours of my time, and was not willing to try and debug the problem).
So, I switched back to Wordpress (never really switched now, did I). I got it up and running in about 5-10 minutes. I WILL give DasBlog another try sometime in the future.
[ad] It’s advisable to install data recovery software on your hosting server. If your hosting company doesn’t support data recovery hardware, you might loss your entire word press site in case of a crash. And if you don’t have a computer backup device, it would be difficult to install windows backup software. A simple online file sharing is still an option there.
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
October 4th, 2007 at 2:26 pm
I’ve been having exactly the same problem. I’m a .NET developer; ideally I’d like a .NET blog, so I can customise it and make it my own.
WordPress took me about 5 minutes to setup, literally. Just create an empty MySql database, upload the files via ftp, browse to the site, and there it is - working, nothing else to do.
So then I try out blogengine.net, repeat the above steps…what do i get? errors. so i fix the errors, then i get more errors, i fix those, and then i get a site that occasionally hits more errors as i try out new bits of functionality. So then i think “I don’t have time for this”, and give up! To be fair to BlogEngine, it was exactly the same deal with Subtext & DasBlog. And, to be fair to all of the .NET blogs, these problems are partially down to the fact that I’m on shared hosting.
Given my situation I prefer to use WordPress, because it works out of the box, has very impressive features and a nicely organised admin panel, and is shared-hosting-friendly.
October 4th, 2007 at 2:47 pm
And over time as I have worked more and more with Wordpress, I have learned how to customize it to my liking; PHP is not that hard and you can always look online for the occasional syntax help required.
June 20th, 2008 at 4:42 am
Delie the key to have a .net blog is finding a .net host that know what they are doing so they can support you and your .net applications. I host my .net sites with Server Intellect and if I a code issue they can resolve my issues pretty quickly. I also recommend not going with shared=)
June 20th, 2008 at 8:55 am
Well, yes… but anything beyond shared is too much (costwise) for most of us….
August 10th, 2008 at 12:11 pm
You should really consider BlogEngine.Net. Check out my comparison of BlogEngine.Net Vs WordPress