With the release of dasBlog 2.0 very close, I updated my dasBlog importer for BlogML files. You can now specify the source and destination of the import and export, instead of having to make changes in the sourcecode.

The actual code to import and export the content is not changed since the previous release. Use at your own risk and always make a backup.

[update:] Replaced the zip with a new version using the final dasBlog 2.0 binaries.

And we have an UI.

The BlogML import/export functionality for dasBlog is planned for a future release, but as soon as the project has officially moved to Asp.Net 2.0 it will be available in svn and the dailybuilds.

What features do you want for the import and export functionality? Currently it's an all or nothing operation, but things like selecting a date range for the export could be useful. And other suggestions?

BlogML is an XML format for storing the contents of a blog; either for archival or migrating to a different blogging engine.

BlogML currently supports the following engines:

• Community Server
• Subtext
• SingleUserBlog

And I finished a beta implementation for dasBlog today.

The current BlogML format does not support all the features dasBlog has, so the following information is lost when exporting your blog using BlogML:

• Post specific languages; the language information for a post made in a different language than the default is lost;
• Only trackbacks are exported; Pingbacks and referrals are lost; 
• Attachments are not imported in this build;
• Some properties of comments are lost (useragent, ip of user);

The current driver program is very basic, and requires some hacking to switch between import- and export-mode.

Note: although dasBlog is a .Net 1.1 project, this is written using .Net 2.0 as per the BlogML project.

download: dasblogml.zip