<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Traversing SharePoint List Folder Hierarchies</title>
	<atom:link href="http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/</link>
	<description>It's a household name</description>
	<lastBuildDate>Wed, 03 Mar 2010 04:54:37 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: HSarioglu</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7355</link>
		<dc:creator>HSarioglu</dc:creator>
		<pubDate>Tue, 02 Jun 2009 07:53:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7355</guid>
		<description>Thanks a lot. &quot;Moving SPListItem&quot; solution is wonderful. Thanks again.</description>
		<content:encoded><![CDATA[<p>Thanks a lot. &#8220;Moving SPListItem&#8221; solution is wonderful. Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SharePoint Buzz</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7304</link>
		<dc:creator>SharePoint Buzz</dc:creator>
		<pubDate>Mon, 13 Apr 2009 01:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7304</guid>
		<description>&lt;strong&gt;Quick Links Krichie Edition...&lt;/strong&gt;

There were a few posts that I found interesting on Krichie - ......</description>
		<content:encoded><![CDATA[<p><strong>Quick Links Krichie Edition&#8230;</strong></p>
<p>There were a few posts that I found interesting on Krichie &#8211; &#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Richie</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7217</link>
		<dc:creator>Keith Richie</dc:creator>
		<pubDate>Mon, 24 Nov 2008 15:10:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7217</guid>
		<description>is that 3000 folders at the same level?</description>
		<content:encoded><![CDATA[<p>is that 3000 folders at the same level?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PrashanthSpark</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7210</link>
		<dc:creator>PrashanthSpark</dc:creator>
		<pubDate>Fri, 21 Nov 2008 04:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7210</guid>
		<description>I have folders around 3000 in my shared document library &amp; it seems very slow when we use via webservice...

how can we tune up this folders in sharepoint to be fast response.

performance is needed right now!

i had created webservice to get site defention which retrives all folders &amp; path enumerating.</description>
		<content:encoded><![CDATA[<p>I have folders around 3000 in my shared document library &amp; it seems very slow when we use via webservice&#8230;</p>
<p>how can we tune up this folders in sharepoint to be fast response.</p>
<p>performance is needed right now!</p>
<p>i had created webservice to get site defention which retrives all folders &amp; path enumerating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holy Nested Root Folder Batman! &#171; Krichie - That SharePoint Guy</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7000</link>
		<dc:creator>Holy Nested Root Folder Batman! &#171; Krichie - That SharePoint Guy</dc:creator>
		<pubDate>Mon, 21 Apr 2008 18:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-7000</guid>
		<description>[...] Nested Root Folder&#160;Batman!  In one of my previous posts, I talked about how I was using the SPQuery object to traverse SharePoint List/Folder [...]</description>
		<content:encoded><![CDATA[<p>[...] Nested Root Folder&nbsp;Batman!  In one of my previous posts, I talked about how I was using the SPQuery object to traverse SharePoint List/Folder [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: =8)-DX</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6997</link>
		<dc:creator>=8)-DX</dc:creator>
		<pubDate>Fri, 18 Apr 2008 09:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6997</guid>
		<description>DanMc: 
&gt;&gt;Being new to SP, I noticed that when I use foreach to enumerate over the Items in a List, that I get huge memory bloat that does not release.

If you use the SPList.Items collection it will theoretically cache ALL the items in the list in memory (SPList objects). In lists with thousands of items this is not optimal, and in large lists it could lead to memory clutter. Much better is to use Views and Queries to return only the required items. I think you can divide the query into batches by setting the SPQuery.ListItemCollectionPosition and SPQuery.RowLimit properties. Basically it all boild down to using the Items collection as little as possible. us ItemCount to get the number of items.

Claudia: 
&gt;&gt;is it possible to add a property to a list folder?

Each SPFolder object in a custom list has a corresponding Item object accessible through SPFolder.Item or SPList.GetItemByUniqueId(SPFolder.Item). You can get the folder&#039;s properties using this SPListItem object just as you would with any other list item.</description>
		<content:encoded><![CDATA[<p>DanMc:<br />
&gt;&gt;Being new to SP, I noticed that when I use foreach to enumerate over the Items in a List, that I get huge memory bloat that does not release.</p>
<p>If you use the SPList.Items collection it will theoretically cache ALL the items in the list in memory (SPList objects). In lists with thousands of items this is not optimal, and in large lists it could lead to memory clutter. Much better is to use Views and Queries to return only the required items. I think you can divide the query into batches by setting the SPQuery.ListItemCollectionPosition and SPQuery.RowLimit properties. Basically it all boild down to using the Items collection as little as possible. us ItemCount to get the number of items.</p>
<p>Claudia:<br />
&gt;&gt;is it possible to add a property to a list folder?</p>
<p>Each SPFolder object in a custom list has a corresponding Item object accessible through SPFolder.Item or SPList.GetItemByUniqueId(SPFolder.Item). You can get the folder&#8217;s properties using this SPListItem object just as you would with any other list item.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Richie</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6996</link>
		<dc:creator>Keith Richie</dc:creator>
		<pubDate>Thu, 17 Apr 2008 18:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6996</guid>
		<description>I believe you can.  You just need to create a new content type based on the folder content type, and add the columns that you require to the folder.</description>
		<content:encoded><![CDATA[<p>I believe you can.  You just need to create a new content type based on the folder content type, and add the columns that you require to the folder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6990</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Mon, 07 Apr 2008 18:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6990</guid>
		<description>Keith, is it possible to add a property to a list folder? I&#039;m asking this because I need to show the items and folders of a Sharepoint list in an application outside Sharepoint. They have to be shown in a specific order, something like this:

Item #1
Folder #1
      Subitem #1
      Subitem #2
      Subitem #3
Item #2
Item #3
Folder #2
      Subitem #1
      Subitem #2
Item #4
Item #5

So I thought of solving this by using a property (or something of the sort) in the folder, just like a column in the list item, to store the display sequence number.

How can I do that?</description>
		<content:encoded><![CDATA[<p>Keith, is it possible to add a property to a list folder? I&#8217;m asking this because I need to show the items and folders of a Sharepoint list in an application outside Sharepoint. They have to be shown in a specific order, something like this:</p>
<p>Item #1<br />
Folder #1<br />
      Subitem #1<br />
      Subitem #2<br />
      Subitem #3<br />
Item #2<br />
Item #3<br />
Folder #2<br />
      Subitem #1<br />
      Subitem #2<br />
Item #4<br />
Item #5</p>
<p>So I thought of solving this by using a property (or something of the sort) in the folder, just like a column in the list item, to store the display sequence number.</p>
<p>How can I do that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DanMc</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6984</link>
		<dc:creator>DanMc</dc:creator>
		<pubDate>Wed, 26 Mar 2008 17:13:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6984</guid>
		<description>Keith, thanks for the quick reply.  I will take a look at the article, but I am already properly disposing of my Web and Site references.
Is there a way we can take this conversation &quot;off-line&quot; so as to not clutter up your blog?</description>
		<content:encoded><![CDATA[<p>Keith, thanks for the quick reply.  I will take a look at the article, but I am already properly disposing of my Web and Site references.<br />
Is there a way we can take this conversation &#8220;off-line&#8221; so as to not clutter up your blog?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Richie</title>
		<link>http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6981</link>
		<dc:creator>Keith Richie</dc:creator>
		<pubDate>Wed, 26 Mar 2008 12:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.krichie.com/2007/01/30/traversing-sharepoint-list-folder-hierarchies/#comment-6981</guid>
		<description>Not sure the direct calls your making during the enumeration, but if you are accessing the lists ParentWeb, it will instantiate a new SPWeb instance that you should call dispose on.
See: &quot;Best Practices: Using Disposable Windows SharePoint Services Objects&quot;
http://msdn2.microsoft.com/en-us/library/aa973248.aspx

Article was written for WSS 2.0/SPS2003 but still applies to WSS 3.0/MOSS</description>
		<content:encoded><![CDATA[<p>Not sure the direct calls your making during the enumeration, but if you are accessing the lists ParentWeb, it will instantiate a new SPWeb instance that you should call dispose on.<br />
See: &#8220;Best Practices: Using Disposable Windows SharePoint Services Objects&#8221;<br />
<a href="http://msdn2.microsoft.com/en-us/library/aa973248.aspx" rel="nofollow">http://msdn2.microsoft.com/en-us/library/aa973248.aspx</a></p>
<p>Article was written for WSS 2.0/SPS2003 but still applies to WSS 3.0/MOSS</p>
]]></content:encoded>
	</item>
</channel>
</rss>
