<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by rharik</title>
    <description>Stories kicked by rharik</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>Fluent hierarchical construction</title>
      <description>Building a hierarchy of objects doesn't happen that often in code, but when it does, it can get pretty ugly.  Most of the time, the hierarchy will come out of the database.  Recently, we had a hierarchy that needed to be built straight in code.  We had something like this going on: &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fwww.lostechies.com%2fblogs%2fjimmy_bogard%2farchive%2f2008%2f10%2f15%2ffluent-hierarchical-construction.aspx"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fwww.lostechies.com%2fblogs%2fjimmy_bogard%2farchive%2f2008%2f10%2f15%2ffluent-hierarchical-construction.aspx" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/aspnet/Fluent_hierarchical_construction</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/aspnet/Fluent_hierarchical_construction</guid>
      <pubDate>Thu, 16 Oct 2008 10:57:53 GMT</pubDate>
    </item>
  </channel>
</rss>