DasBlog

See Scott Hanselman This weblog is sponsored by DasBlog.

See Omar Shahine This weblog is sponsored by DasBlog.

(Repost of Scott Hanselman blog post) Omar pulled the trigger and we released DasBlog 1.9.6264. Why 6264 you ask? Because it's 2006 and the 264th day, that's why. Download it. Here's some of the new features. Much better ... [More] multi-user/blogger support including a Top Posters macro and total comments - from Christoph De Baene TagCloud Support - from Scott Support for Mobile Browsers like Blackberries and SmartPhones - from Scott Note the large section in your web.config and the mobile theme that is required for this support. Huge (100x ) speedup in Macro execution - from Scott Support for If-Not-Modified to speed up execution, improve RSS bandwidth and CPU cycles - from Scott Direct Feedburner Support with 301 redirection for RSS and Atom feeds. Don't lose a single subscriber. We're the only blog with direct support for Feedburner and Feedflare I believe. - from Scott I encourage you to check out FeedBurner. You can add FeedFlare to your posts, and modify your feed in ways DasBlog can't. They also handle your Feed bandwidth and provide rich statistics. It's free ($ for advanced stats) and it's very powerful. Do be aware that when you make the decision to move over to FeedBurner your existing feeds will start redirecting folks to FeedBurner immediately. That's part of the power of the whole thing, but be warned. Delete comments directly from your mail reader - from Omar Comment moderation option New themes out of the box, 18 at last count - from Many Folks New XML-RPC support for newMediaObject and new version of XML-RPC.NET from Charles Cook - from Omar and Giuseppe Dipietro Macros for Next Post and Previous Post - Justice Gray Check the DasBlog theme or add this line to the top of your itemtemplate.blogtemplate. <%PreviousLink("&laquo;&nbsp;",25)%><%MainPageEntryLink("Main", "|")%><%NextLink("&nbsp;&raquo;",25)%><br/> A few security and XSS fixes Support for Gravatars, images of your choosing that appear next to your comments - John Forsythe Support for limited HTML markup in comments Emails removed to avoid having email addresses stolen from Feeds Added an Email page for leaving comments to the author, includes Captcha New support for RSD so client software can autoconfigure itself - from Omar Pluggable Rich Text Editor, choose from the latest version of FreeTextBox or FCKEditor or write your own adapter - from Josh Flanagan Support for alternate SMTP ports We work with Windows Live Writer out of the box - from Omar Support for CoComment - from Scott Microsummary support for Firefox 2.0 Beta - from Scott Organized source, build, and packing for clarity - from Josh Flanagan New Feed Icons - from Omar Autometic generation of Google SiteMaps - from Scott Automatic disabling of Comments after a certain number of days. Also manual "close comments" support - from Omar ContentLookAhead show future dated posts - from Josh Flanagan Other fixes and suggestions from Tomas Restrepo, Jason Follas, Rene Lebherz and Steven Rockarts. Added entry CPU usage optimizatons from George V. Reilly. Ajax Autosave Drafts support from Steven Rockarts and Justice Gray. Better strings and support for German from Alexander Groß, Portuguese from Adelino Araújo, and Vietnamese from Phạm Đức Hải. Many great new themes Updated readme.rtf from Tim Sherill Single-handed support of DasBlog.info and DasBlog.us to the enthusiastic and tireless Tom Watts! Welcome to new team members Alexander Groß, Paul Van Brenck, and John Forsythe who really did a lot of work to make this release possible! Thanks to Jacob Proffitt for doing some crazy debugging of caching on FireFox that will be in a point release soon. New DasBlog Badges/Artwork from Alexander Groß...download them here: File Attachment: DasBlog Artwork.zip (1015 KB) Thanks again to all who jumped in this release. The number of bug fixes and patches was fantastic. If you are starting from scratch, READ THE README. If you are upgrading, always back up your whole site. You have a number of choices on how to upgrade but mostly it's just merge the web.config and copy over everything else. Read the readme.rtf. If you have made changes to your web.config, manually merge your existing web.config with the one we ship, using a tool like Beyond Compare. If you are running DasBlog 1.8, you don't need to run the DasBlog Upgrader if you don't want to. It'll clean up spam and tighten up your content, but it's not required. If you've modified your themes or an included theme with DasBlog, back up your stuff so you can merge in new features as you like. DasBlog is written in ASP.NET 1.1 but runs under 1.1 or 2.0. Read the readme.rtf and the web.config for details. Some things to note: File bugs here. Submit patches here. Here's how to submit a patch and get the source code. Daily builds (if you like living on the edge) are here. Some folks have said that DasBlog isn't actively developed because we are slow to release. Do join our mailing list, our checkin list and check out the daily builds. Join our developers mailing list (very active) here. Subversion Checkin mailing list is here. If you want to extend DasBlog... You can always write your own THEME You can write custom macros...here's a writeup from Kris van der Mast on how, and a number of nice macros from Vasanth Dharmaraj including his tutorial. Regarding Macros: The best documentation for the Macros (so far) is the Macros.cs file itself. Nearly every public function in there is a potential macro you can use in your templates. If you wish a Macro existed, perhaps it already does. You can browse the code in the Subversion Repository without installing anything. Here's a link directly to the Macros.cs file. We're always looking for help editing the documentation and working on http://dasblog.info/. We also appreciate folks who answer questions in the forums at http://dasblog.us/. This weblog is sponsored by DasBlog. [Less]

We finally have a real home page, and yes its also generated by dasBlog, while dasBlog is a blogging engine and does not aspire to be CMS system, its amazing what you can do with dasBlog! Send your comments too: This weblog is sponsored by DasBlog.

[Article by Grz, Kris. http://blog.krisvandermast.com/CreatingCustomMacrosForDasBlog.aspx] dasBlog is a decent blogging engine originally created by Clemens Vasters. A nice thing that not many people seem to be aware of is that you can easily ... [More] extend it by creating custom macros. Such a custom macro isn't anything else than just a class library that you can hook into your copy of dasBlog and use it later on in one of the available templates that make up the website. I couldn't really find a lot of information about this, so I decided to create my own article about the subject that also puts in the solutions I found.  Also I would like to show the code that I use in my current installment that's reusable directly for other dasBlog users. Creation: So, as I already mentioned, creating macros is just like creating a class library. So lets fire up vs.net, create a new project and in the templates choose Class library like in Figure 1. The name of the project is also important when we will be configuring dasBlog to let it know about the existence of our macros. I chose My dasBlog Macros but you can choose your own name of course. Figure 1: Create a new project based upon the Class Library template. If you haven't downloaded the code for dasBlog now's a good time to do so. You can download the bits from the official site(1) or you can use the guideline to get the latest bits and pieces(2) like I did. Now we have to add 3 references in order to be able to create our custom macro. You do this by right clicking in the Solution Explorer of Visual Studio.NET on the References node. Take a look at Figure 2 to choose System.Web, and Figure 3 to choose 2 assemblies that are from dasBlog itself. These 2 are newTelligence.DasBlog.Runtime and newTelligence.DasBlog.Web.Core. The result is shown in Figure 4. Figure 2: locate and choose System.Web Figure 3: Navigate to the bin folder of the compiled bits of dasBlog and select the needed assemblies. Figure 4: After adding the needed references. In Figure 4 you can also see that I deleted the default Class1.cs file and added a new class with the name Macros.cs. This is the only class we'll need for the moment. Here's the code for the Macros class:     1 using System;     2 using System.Collections.Generic;     3 using System.Text;     4 using System.Web.UI;     5 using newtelligence.DasBlog.Runtime;     6 using newtelligence.DasBlog.Web.Core;     7      8 namespace MydasBlogMacros     9 {    10     public class MyMacros    11     {    12         protected SharedBasePage sharedBasePage;    13         protected Entry currentEntry;    14     15         public MyMacros(SharedBasePage page, Entry entry)    16         {    17             sharedBasePage = page;    18             currentEntry = entry;    19         }    20     21         public virtual Control EmailIt(string linkText, string cssStyle)    22         {    23             if (this.currentEntry != null)    24             {    25                 string link = this.currentEntry.Link != null    26                     ? this.currentEntry.Link : Utils.GetPermaLinkUrl(this.currentEntry);    27     28                 return new LiteralControl("<a href=\"mailto:?subject=" this.currentEntry.Title    29                     "&body=I found this to be a great read: " link    30                     ". Hope you like it too.\" class=\""    31                     cssStyle "\">" linkText "</a>");    32             }    33     34             return new LiteralControl("");    35         }    36     37         public virtual Control Delicious(string linkText, string cssStyle)    38         {    39             if (this.currentEntry != null)    40             {    41                 string link = this.currentEntry.Link != null    42                     ? this.currentEntry.Link : Utils.GetPermaLinkUrl(this.currentEntry);    43     44                 return new LiteralControl("<a href=\"http://del.icio.us/post?url=" link    45                       "&title=" this.currentEntry.Title "\" class=\"" cssStyle "\">"    46                     linkText "</a>");    47             }    48     49             return new LiteralControl("");    50         }    51     52         public virtual Control Digg(string linkText, string cssStyle)    53         {    54             string link = this.currentEntry.Link != null    55                     ? this.currentEntry.Link : Utils.GetPermaLinkUrl(this.currentEntry);    56     57             return new LiteralControl("<a href=\"http://www.digg.com/submit?url=" link    58                 "\" class=\"" cssStyle "\">"    59                 linkText "</a>");    60         }    61     62         public virtual Control Technorati(string linkText, string cssStyle)    63         {    64             if (this.currentEntry != null)    65             {    66                 string link = this.currentEntry.Link != null    67                     ? this.currentEntry.Link : Utils.GetPermaLinkUrl(this.currentEntry);    68     69                 return new LiteralControl("<a href=\"http://www.technorati.com/search/"    70                     this.currentEntry.Title    71                     "\" class=\"" cssStyle "\">"    72                     linkText "</a>");    73             }    74     75             return new LiteralControl("");    76         }    77     }    78 } Note that the signature in the constructor is required in order to let the macros work! Besides the constructor I created 4 methods, which will be the macros eventually, the first one EmailIt is for creating a link with the url of the current item in the body so someone can easily mail it to someone whom (s)he thinks will also be interested in the article. The other 3 are for well known web 2.0 services: del.icio.us, digg and technorati. The methods/macros take all 2 input parameters: the string to appear in the link and the css style that will go in the class attribute of the rendered tag. Separating content and layout has several benefits: it's easy to update in a single place and an external .css file can be cached on the client. After compiling the source code, preferably in Release mode, and after that open windows explorer and navigate to where the .dll file is created. By default this will be the place where you created your project and in there the subfolders /bin/Release. Now copy the .dll file to the /bin subfolder of the dasBlog solution (this is the same folder where you got your references from). Configure dasBlog: We created our macros assembly, dropped it in the dasBlog folder, but we still need to configure dasBlog in such a way that it knows of the existance of our macros. This is entirely done in the web.config file that can be found in the root folder of dasBlog. Open it with your favorite IDE and uncomment the following line at the top of the web.config: <section name="newtelligence.DasBlog.Macros" type="newtelligence.DasBlog.Web.Core.MacroSectionHandler, newtelligence.DasBlog.Web.Core" /> Now navigate to the tag <newtelligence.DasBlog.Macros>, uncomment it and add this line: <add macro="mymacros" type="MydasBlogMacros.MyMacros, MydasBlogMacros"/> Remember I told in the previous part that you could name your solution somewhat else, well here that name comes into play. If you take a look at the previous line you can see this combination: type="TypeName, Name of the assembly". TypeName in this case is NameSpace.ClassName. The name in the macro attribute, in this example mymacros will be used when we want to use a specific macro. Use the macro in your template: So at this point we created our macros, configured dasBlog that they exist. Now comes the part where we embed, or better use, our macros so they become visible in the what a visitor can see by altering the templates in the themes. dasBlog ships with several themes out of the box and people can switch between them. You can however push visitors to only have one theme available by deleting the rest of the themes. If you don't this you'll need to do the next steps for every theme if you want those themes to also have your macros available. Navigate to the theme folder of choice. There you'll see several .css files and 3 files that have the extension .blogtemplate. Because the macros will be used for every item, they contain specific information for a specific item, open the itemTemplate.blogtemplate file. Here you can call a macro with the following syntax: <%EmailIt("Email it!", "mailLinkStyle")|mymacros%>. The call can be easily identified, it's the first macro in our example EmailIt. The method takes 2 parameters. After the method call you see the | followed by the name we provided in the macro attribute when we configured the web.config. I also created a new external .css file where I put the specific styles. After that I imported the newly created file into the base.css file with this statement: @import url("mymacros.css"); Resources: - (1): dasBlog download. - (2): Compiling the dasBlog source code. - The class FooMacros in the dasBlog total solution. - Creating dasBlog macros. Article by Grz, Kris. http://www.dasblog.info/ct.ashx?id=6a4dac85-0d2c-4765-bf73-4307e44ace6a&url=http://blog.krisvandermast.com/CreatingCustomMacrosForDasBlog.aspx This weblog is sponsored by DasBlog. [Less]

Anti-Spam Features Automatic Referral and Trackback blacklist update CAPTCHA for non-admin users (Font warping has also been increased in this version) Logging and display of Comment IP addresses and resolved Hostnames for Admins ... [More] DasBlogUpgrader can strip spam from existing content folders Support for rel="nofollow" Ability to delete referrals and trackbacks directly from the Admin UI Delete comments directly from your mail reader Comment moderation option RSS Emails removed to avoid having email addresses stolen from Feeds Support for AKISMET (next release) Security Features HttpOnly cookies Admin access auditing SMTP Authentication for outgoing mail Syndication Features Improved RSS Comments support for SharpReader and RSS Bandit Upgraded Atom support from 0.3 to Valid Atom 1.0. ATOM Syndication permalink changes but 301 is issued. RSS 2.0 and Atom 1.0 validates via FeedValidator. Ability to mark entries as "syndicated" or not. Entries can appear on the site but not in RSS/Atom. New between RC1 and Gold: Plugable, configurable pinging of Blog Search engines like pubsub and technorati. Channel Image feature (RSS Bug) Direct Feedburner Support with 301 redirection for RSS and Atom feeds. Performance Features Search Highlighting is optional now Referrals are logged but not stored in XML by default. Configurable. (This has huge performance benefits for high traffic sites.) dasBlog Upgrader can optionally remove all referrals. (Again with high traffic sites some folks had 5meg XML files full of referrals) Theme templates are now cached in memory. Log files are archived daily to .zip files. Support for Really Simple Discovery (RSD) so client software can autoconfigure itself Support for alternate SMTP ports Installation Features VBS for IIS permissions and VDir creation Support for running under ASP.NET 2.0 Support for running on Win2k 2003 without changing permissions when impersonation is enabled dasBlogBlogXContentImporter tool Content Features Ability to pre- and post-date entries Cross Posting (post is added two blogs at once) Permalinks based on Title and Date optional: 2005/06/06/title.aspx Latest build of Free Text Box including ability to upgrade FTB without upgrading DasBlog. Text Editor (FTB) supports IE7 Text Editor (FTB) supports FireFox Blog Statistics Log Blog Statistics macro Archive pages macro macro for items disclaimer macro for homePageTemplate disclaimerLink Mail-To-Weblog continues to improves. Works with Thunderbird. Upload Image and Upload Attachment Comments can now be "closed" for a given Entry Entries can be set to IsPublic (i.e. working drafts before release) Large calendar view with posts Blogroll.aspx for rendering your blogroll.opml file TrackBack Autodiscovery is attempted before PingBack Autodiscovery Pingbacks from one dasBlog to another dasBlog work TagCloud Support Support for Mobile Browsers like Blackberries and SmartPhones Top Posters macro and total comments Macros for Next Post and Previous Post Macro for Category Paging (next release) Support for Gravatars Support for limited HTML markup in comments Email page for leaving comments to the author, includes Captcha Pluggable Rich Text Editor, choose from the latest version of FreeTextBox or FCKEditor or write your own adapter Multi-user/blogger support Emailed Daily Activity Reports Support for Blogging directly from Word 2007 DHTML Timeline of Posts from the MIT Simile project Support for SMTP Servers like Gmail for notifications (and alternate SMTP ports) LiveComment Preview Category and Home Page Paging Macros Extensibility Features Custom Macro Plugin model without recompiling DasBlog (see the source for the example custom macro) Works with Windows Live Writer out of the box Support for CoComment Microsummary support for Firefox 2.0 Beta Automatic generation of Google SiteMaps Automatic disabling of Comments after a certain number of days. Also manual "close comments" support ContentLookAhead show future dated posts Ajax Autosave Drafts support Theme Features dasBlog now ships with 24 themes and a Theme Combo to change between them. theme.manifest file makes themes and image assets more portable. dasBlog Badges/Artwork Architecture ASP.NET 2.0, C# Medium Trust model Operational under ASP.NET 2.0 and ASP.NET 3.0 Structured XML data store Supports template themes (Ships with over 24) This weblog is sponsored by DasBlog. [Less]

Copyright (c) 2003, newtelligence AG. (http://www.newtelligence.com) Original BlogX Source Code: Copyright (c) 2003, Chris Anderson (http://simplegeek.com) All rights reserved. Redistribution and use in source and binary forms, with ... [More] or without modification, are permitted provided that the following conditions are met: (1) Redistributions of source code must retain the above copyright notice, this list ofconditions and the following disclaimer. (2) Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. (3) Neither the name of the newtelligence AG nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ------------------------------------------------------------------------- Original BlogX source code (c) 2003 by Chris Anderson (http://simplegeek.com) newtelligence is a registered trademark of newtelligence Aktiengesellschaft. For portions of this software, the some additional copyright notices may apply which can either be found in the license.txt file included in the source distribution or following this notice. -------------------------------------------------------------------- Copyright (c) 2003 Chris Anderson This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose,including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. This weblog is sponsored by DasBlog. [Less]

Since dasBlog is an open source project and we are all volunteers, please do not contact us at our personal e-mail addresses for support or at out personal blogs, (of course comments and appropriate contributions at our blogs is appreciated). ... [More] For support: Please use the self help forums, the developer e-mail lists (developer issues only), and as a last resort for other issues we will try to respond here: Thanks dasBlog Team > This weblog is sponsored by DasBlog. [Less]

(Repost of Scott Hanselman blog post) Omar pulled the trigger and we released DasBlog 1.9.6264. Why 6264 you ask? Because it's 2006 and the 264th day, that's why. Download it. Here's some of the new features. Much better ... [More] multi-user/blogger support including a Top Posters macro and total comments - from Christoph De Baene TagCloud Support - from Scott Support for Mobile Browsers like Blackberries and SmartPhones - from Scott Note the large section in your web.config and the mobile theme that is required for this support. Huge (100x ) speedup in Macro execution - from Scott Support for If-Not-Modified to speed up execution, improve RSS bandwidth and CPU cycles - from Scott Direct Feedburner Support with 301 redirection for RSS and Atom feeds. Don't lose a single subscriber. We're the only blog with direct support for Feedburner and Feedflare I believe. - from Scott I encourage you to check out FeedBurner. You can add FeedFlare to your posts, and modify your feed in ways DasBlog can't. They also handle your Feed bandwidth and provide rich statistics. It's free ($ for advanced stats) and it's very powerful. Do be aware that when you make the decision to move over to FeedBurner your existing feeds will start redirecting folks to FeedBurner immediately. That's part of the power of the whole thing, but be warned. Delete comments directly from your mail reader - from Omar Comment moderation option New themes out of the box, 18 at last count - from Many Folks New XML-RPC support for newMediaObject and new version of XML-RPC.NET from Charles Cook - from Omar and Giuseppe Dipietro Macros for Next Post and Previous Post - Justice Gray Check the DasBlog theme or add this line to the top of your itemtemplate.blogtemplate. <%PreviousLink("&laquo;&nbsp;",25)%><%MainPageEntryLink("Main", "|")%><%NextLink("&nbsp;&raquo;",25)%><br/> A few security and XSS fixes Support for Gravatars, images of your choosing that appear next to your comments - John Forsythe Support for limited HTML markup in comments Emails removed to avoid having email addresses stolen from Feeds Added an Email page for leaving comments to the author, includes Captcha New support for RSD so client software can autoconfigure itself - from Omar Pluggable Rich Text Editor, choose from the latest version of FreeTextBox or FCKEditor or write your own adapter - from Josh Flanagan Support for alternate SMTP ports We work with Windows Live Writer out of the box - from Omar Support for CoComment - from Scott Microsummary support for Firefox 2.0 Beta - from Scott Organized source, build, and packing for clarity - from Josh Flanagan New Feed Icons - from Omar Autometic generation of Google SiteMaps - from Scott Automatic disabling of Comments after a certain number of days. Also manual "close comments" support - from Omar ContentLookAhead show future dated posts - from Josh Flanagan Other fixes and suggestions from Tomas Restrepo, Jason Follas, Rene Lebherz and Steven Rockarts. Added entry CPU usage optimizatons from George V. Reilly. Ajax Autosave Drafts support from Steven Rockarts and Justice Gray. Better strings and support for German from Alexander Groß, Portuguese from Adelino Araújo, and Vietnamese from Phạm Đức Hải. Many great new themes Updated readme.rtf from Tim Sherill Single-handed support of DasBlog.info and DasBlog.us to the enthusiastic and tireless Tom Watts! Welcome to new team members Alexander Groß, Paul Van Brenck, and John Forsythe who really did a lot of work to make this release possible! Thanks to Jacob Proffitt for doing some crazy debugging of caching on FireFox that will be in a point release soon. New DasBlog Badges/Artwork from Alexander Groß...download them here: File Attachment: DasBlog Artwork.zip (1015 KB) Thanks again to all who jumped in this release. The number of bug fixes and patches was fantastic. If you are starting from scratch, READ THE README. If you are upgrading, always back up your whole site. You have a number of choices on how to upgrade but mostly it's just merge the web.config and copy over everything else. Read the readme.rtf. If you have made changes to your web.config, manually merge your existing web.config with the one we ship, using a tool like Beyond Compare. If you are running DasBlog 1.8, you don't need to run the DasBlog Upgrader if you don't want to. It'll clean up spam and tighten up your content, but it's not required. If you've modified your themes or an included theme with DasBlog, back up your stuff so you can merge in new features as you like. DasBlog is written in ASP.NET 1.1 but runs under 1.1 or 2.0. Read the readme.rtf and the web.config for details. Some things to note: File bugs here. Submit patches here. Here's how to submit a patch and get the source code. Daily builds (if you like living on the edge) are here. Some folks have said that DasBlog isn't actively developed because we are slow to release. Do join our mailing list, our checkin list and check out the daily builds. Join our developers mailing list (very active) here. Subversion Checkin mailing list is here. If you want to extend DasBlog... You can always write your own THEME You can write custom macros...here's a writeup from Kris van der Mast on how, and a number of nice macros from Vasanth Dharmaraj including his tutorial. Regarding Macros: The best documentation for the Macros (so far) is the Macros.cs file itself. Nearly every public function in there is a potential macro you can use in your templates. If you wish a Macro existed, perhaps it already does. You can browse the code in the Subversion Repository without installing anything. Here's a link directly to the Macros.cs file. We're always looking for help editing the documentation and working on http://dasblog.info/. We also appreciate folks who answer questions in the forums at http://dasblog.us/. This weblog is sponsored by DasBlog. [Less]

We finally have a real home page, and yes its also generated by dasBlog, while dasBlog is a blogging engine and does not aspire to be CMS system, its amazing what you can do with dasBlog! Send your comments too: This weblog is sponsored by DasBlog.