Scott Hanselman

Folks switching to DasBlog

May 11, 2005 Comment on this post [8] Posted in ASP.NET | DasBlog
Sponsored By

Just a small observation, as I was catching up on feeds today, I noticed that both Anil John and Larry O'Brien switched over to DasBlog. How cool is that? Have you switched lately?

Powerful stuff. DasBlog, we suck less!

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service
May 11, 2005 7:16
Darn tootin' right :-)

I've been using DasBlog for my internal work blog for a while. I'd wanted to make the switch earlier but a combination of inertia and lack of good migration tools from .TEXT was stopping me.

Got over the interia when Community Server came out :-)

Reasons for switching:

* Optimized for a single blog
* XCOPY deployable
* Site Search
* Mail-To-Weblog
* Upgrade process seems to be very clean per people who currently use it and upgraded over the last couple of revs.
* Actively maintained and updated (Big Deal to Me)

And from a personal perspective, I take a great deal of comfort in that there seems to be an actual configuration and release managment process in place for bugfixes and updates.

Good work, Scott!
May 11, 2005 7:44
I'm thinking of switching from Movable Type to DasBlog. Is anyone aware of any tools to assist in the conversion?
May 11, 2005 12:30
Absolutely, I have move from .Text to dasBlog and have been very impressed. I tried community server but its huge and branded, I don't need either of those. Bonus I can ditch sql support on my hosting and get a price reduction next year too.

I do miss the "archive" style of dotText though not a fan of the calendar and there doesnt seem to be a macro for dottext style archives, but for all the gains I get with dasBlog I can live with the calendar until I write my own replacement bit.

Thanks all to all the dasBlog guys for this tool. And so easy to install.

May 11, 2005 14:31
.TEXT has been inactive for quite awhile now, and Community Server is a beast when all I want is a blog. While CS is scalable to many blogs, galleries, and forums, unfortunately, it's not scalable to single blog-only very easily without what some would consider hacks.
May 11, 2005 15:04
I recently switched from Blogger to DasBlog. I've got a couple posts on porting content and redirecting old traffic here:

Rick H.
May 11, 2005 16:34
I moved from .Text to DasBlog as well, used the DotText2DasBlog importer to bring in my posts, but have been too lazy to tidy up permalinks that I'm getting 404's on.

All in all DasBlog is very nice. Though category display on "C#" (remove the quotes) is broken on my blog and I've still not been able to verify through documentation that dasBlog does not create trackbacks automatically for links listed in posts (but I've been wrong before...)
May 12, 2005 20:29
I switched from a blogging site to running DasBlog and have never looked back. It was easy to set up, didn't require any extra tools since the data is file driven. My only frustration in getting it set up was setting the permissions correctly. Other than that, it just works.

I agree with SimonT about the calendar. If you're an infrequent poster like me, having the calendar is of little use. I'm about ready to remove it from my page, but haven't spent the time. There is an 'Archives.aspx' page in DasBlog which I really like, but the link to it is not in the default theme.

I've even made a couple of modifications to the code base (for my own evil purposes) and found it very easy to recompile and deploy.
May 13, 2005 10:57
Jason and others, if you want the archive list like .Text has, all you need to do is include the macro "<%newtelligence.drawArchiveMonths()%>" someone within the home template of the them you are using. On my skin, I got rid of the calendar altogether (quite similar to Scott in fact).

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.