<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.sharepointblogs.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SharePoint FieldNotes (Steve Curran)</title><link>http://www.sharepointblogs.com/smc750/default.aspx</link><description>Field notes on Sharepoint 2007 development and other .Net technologies such as reflection</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP2 (Build: 20611.960)</generator><item><title>Advanced Search retreats</title><link>http://www.sharepointblogs.com/smc750/archive/2008/08/21/advanced-search-retreats.aspx</link><pubDate>Thu, 21 Aug 2008 14:54:00 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:20074</guid><dc:creator>steveC</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=20074</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2008/08/21/advanced-search-retreats.aspx#comments</comments><description>Technorati Tags: MOSS , Search In software development one of the key rules is not to take functionality away from users. However, if you do then you should document the fact. The new infrastructure update removes the &amp;quot;Contains&amp;quot; and &amp;quot;Does...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2008/08/21/advanced-search-retreats.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=20074" width="1" height="1"&gt;</description></item><item><title>SPWeb.ProcessBatchData. A list is a list is a list?</title><link>http://www.sharepointblogs.com/smc750/archive/2008/04/03/spweb-processbatchdata-a-list-is-a-list-is-a-list.aspx</link><pubDate>Thu, 03 Apr 2008 17:40:05 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:14875</guid><dc:creator>steveC</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=14875</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2008/04/03/spweb-processbatchdata-a-list-is-a-list-is-a-list.aspx#comments</comments><description>Technorati Tags: SharePoint Development , WSS There is a lot of material on the Internet about the Microsoft.SharePoint.SPWeb.ProcessBatchData method. It is a great method for processing a lot of commands against a SPList without having to open a SPListItemCollection...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2008/04/03/spweb-processbatchdata-a-list-is-a-list-is-a-list.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=14875" width="1" height="1"&gt;</description></item><item><title>Check Outs Gone Crazy</title><link>http://www.sharepointblogs.com/smc750/archive/2008/03/19/check-outs-gone-crazy.aspx</link><pubDate>Wed, 19 Mar 2008 21:25:43 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:14304</guid><dc:creator>steveC</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=14304</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2008/03/19/check-outs-gone-crazy.aspx#comments</comments><description>Technorati Tags: MOSS , WSS , Document Management It seems to be easy to have a lot of documents checked out in SharePoint 2007, yet nobody knows about them except the person who uploaded the document. SharePoint 2007 lets you upload documents first and...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2008/03/19/check-outs-gone-crazy.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=14304" width="1" height="1"&gt;</description></item><item><title>Office 2003 files are second class citizens in SharePoint 2007</title><link>http://www.sharepointblogs.com/smc750/archive/2008/02/26/office-2003-files-are-second-class-citizens-in-sharepoint-2007.aspx</link><pubDate>Tue, 26 Feb 2008 22:17:54 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:13179</guid><dc:creator>steveC</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=13179</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2008/02/26/office-2003-files-are-second-class-citizens-in-sharepoint-2007.aspx#comments</comments><description>Technorati Tags: MOSS WSS Office Document Management There are many ways to upload files to SharePoint 2007 and they all seem to work well. Unless your using Office 2003 or later. Uploading files to SharePoint can be done many ways including the upload...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2008/02/26/office-2003-files-are-second-class-citizens-in-sharepoint-2007.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=13179" width="1" height="1"&gt;</description></item><item><title>SPSiteDataQuery limited to 10 document libraries confirmed by Microsoft</title><link>http://www.sharepointblogs.com/smc750/archive/2008/01/25/spsitedataquery-limited-to-10-document-libraries-confirmed-by-microsoft.aspx</link><pubDate>Fri, 25 Jan 2008 21:07:01 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:11882</guid><dc:creator>steveC</dc:creator><slash:comments>3</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=11882</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2008/01/25/spsitedataquery-limited-to-10-document-libraries-confirmed-by-microsoft.aspx#comments</comments><description>Technorati Tags: WSS SharePoint Search In previous posts I talked about the inaccurate results received when using the SPSiteDataQuery with more than 10 document libraries or lists. http://www.sharepointblogs.com/smc750/archive/2007/07/24/spsitedataquery...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2008/01/25/spsitedataquery-limited-to-10-document-libraries-confirmed-by-microsoft.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=11882" width="1" height="1"&gt;</description></item><item><title>Setting a Custom Edit Form for a Content Type</title><link>http://www.sharepointblogs.com/smc750/archive/2007/11/20/setting-a-custom-edit-form-for-a-content-type.aspx</link><pubDate>Tue, 20 Nov 2007 22:10:54 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:8976</guid><dc:creator>steveC</dc:creator><slash:comments>4</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=8976</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2007/11/20/setting-a-custom-edit-form-for-a-content-type.aspx#comments</comments><description>Technorati Tags: WSS SharePoint This post is about a quirk regarding setting a custom edit form for a content type in a document library. There was a great post by Ton Stegeman http://www.sharepointblogs.com/tonstegeman/archive/2006/10/29/15374.aspx regarding...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2007/11/20/setting-a-custom-edit-form-for-a-content-type.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=8976" width="1" height="1"&gt;</description></item><item><title>SPSiteDataQuery limited to 10 document libraries work around</title><link>http://www.sharepointblogs.com/smc750/archive/2007/11/19/spsitedataquery-limited-to-10-document-libraries-work-around.aspx</link><pubDate>Mon, 19 Nov 2007 22:26:28 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:8910</guid><dc:creator>steveC</dc:creator><slash:comments>3</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=8910</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2007/11/19/spsitedataquery-limited-to-10-document-libraries-work-around.aspx#comments</comments><description>Technorati Tags: WSS SharePoint Search In one of my last posts I talked about the limitations of using SPSiteDataQuery with more than 10 document libraries or lists. http://www.sharepointblogs.com/smc750/archive/2007/07/24/spsitedataquery-limited-to-10...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2007/11/19/spsitedataquery-limited-to-10-document-libraries-work-around.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=8910" width="1" height="1"&gt;</description></item><item><title>Deep Dive SharePoint 2007 Object Model</title><link>http://www.sharepointblogs.com/smc750/archive/2007/09/25/deep-dive-sharepoint-2007-object-model.aspx</link><pubDate>Tue, 25 Sep 2007 14:25:56 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:6307</guid><dc:creator>steveC</dc:creator><slash:comments>5</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=6307</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2007/09/25/deep-dive-sharepoint-2007-object-model.aspx#comments</comments><description>Technorati Tags: MOSS , WSS , SharePoint Development , Discoverability , Testing A big topic these days is about &amp;quot;Discoverability&amp;quot; and the .Net framework. Developers talk about how big the .Net framework has become with 2.0, 3.0 and now 3.5...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2007/09/25/deep-dive-sharepoint-2007-object-model.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=6307" width="1" height="1"&gt;</description></item><item><title>SPSiteDataQuery limited to 10 document libraries or lists</title><link>http://www.sharepointblogs.com/smc750/archive/2007/07/24/spsitedataquery-limited-to-10-document-libraries-or-lists.aspx</link><pubDate>Tue, 24 Jul 2007 16:28:20 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:3387</guid><dc:creator>steveC</dc:creator><slash:comments>15</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=3387</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2007/07/24/spsitedataquery-limited-to-10-document-libraries-or-lists.aspx#comments</comments><description>Technorati Tags: WSS SharePoint Search In previous posts I talked about the pitfalls of searching in WSS or MOSS. I wanted to report one more limitation we have discovered when doing cross-list searches in WSS using the SPSiteDataQuery object. The SPWeb...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2007/07/24/spsitedataquery-limited-to-10-document-libraries-or-lists.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=3387" width="1" height="1"&gt;</description></item><item><title>Making your SharePoint applications Information Management Policy Aware</title><link>http://www.sharepointblogs.com/smc750/archive/2007/07/09/making-your-sharepoint-applications-information-management-policy-aware.aspx</link><pubDate>Mon, 09 Jul 2007 14:35:37 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:2780</guid><dc:creator>steveC</dc:creator><slash:comments>4</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=2780</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2007/07/09/making-your-sharepoint-applications-information-management-policy-aware.aspx#comments</comments><description>Technorati Tags: WSS , MOSS , SharePoint , Information Management Office SharePoint Server 2007 shipped with a powerful new document management feature called &amp;quot;Information Management Policies&amp;quot;. Information management policies can be applied...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2007/07/09/making-your-sharepoint-applications-information-management-policy-aware.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=2780" width="1" height="1"&gt;</description></item><item><title>Custom Cross-List Search Development Pitfalls (Part Two)</title><link>http://www.sharepointblogs.com/smc750/archive/2007/06/20/custom-cross-list-search-development-pitfalls-part-two.aspx</link><pubDate>Wed, 20 Jun 2007 20:20:00 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:2154</guid><dc:creator>steveC</dc:creator><slash:comments>4</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=2154</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2007/06/20/custom-cross-list-search-development-pitfalls-part-two.aspx#comments</comments><description>In my previous post Custom Cross-List Search Development Pitfalls (Part One) I talked about the importance of managing Meta data in order to provide effective ways for users to search for documents. Meta data can be managed via &amp;quot;Managed Properties&amp;quot;...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2007/06/20/custom-cross-list-search-development-pitfalls-part-two.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=2154" width="1" height="1"&gt;</description><category domain="http://www.sharepointblogs.com/smc750/archive/tags/WSS/default.aspx">WSS</category><category domain="http://www.sharepointblogs.com/smc750/archive/tags/Search/default.aspx">Search</category><category domain="http://www.sharepointblogs.com/smc750/archive/tags/MOSS/default.aspx">MOSS</category></item><item><title>Custom Cross List Search Development Pitfalls (Part One)</title><link>http://www.sharepointblogs.com/smc750/archive/2007/06/20/custom-cross-list-search-development-pitfalls-part-one.aspx</link><pubDate>Wed, 20 Jun 2007 20:17:00 GMT</pubDate><guid isPermaLink="false">1f6a1193-f4bb-4480-a5ae-b538d8b20f46:2153</guid><dc:creator>steveC</dc:creator><slash:comments>7</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://www.sharepointblogs.com/smc750/rsscomments.aspx?PostID=2153</wfw:commentRss><comments>http://www.sharepointblogs.com/smc750/archive/2007/06/20/custom-cross-list-search-development-pitfalls-part-one.aspx#comments</comments><description>This is the first of two posts about developing custom cross-list search solutions using either MOSS or WSS 3.0. The two part series will compare and contrast developing cross-list search solutions with MOSS and WSS. This will include issues you should...(&lt;a href="http://www.sharepointblogs.com/smc750/archive/2007/06/20/custom-cross-list-search-development-pitfalls-part-one.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://www.sharepointblogs.com/aggbug.aspx?PostID=2153" width="1" height="1"&gt;</description></item></channel></rss>