<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Michaël&#039;s coding thoughts &#187; SharePoint 2007</title>
	<atom:link href="http://blog.hompus.nl/tag/sharepoint-2007/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hompus.nl</link>
	<description>Because I like to share knowledge</description>
	<lastBuildDate>Fri, 27 Aug 2010 12:10:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Keeping your SharePoint 2010 development databases small</title>
		<link>http://blog.hompus.nl/2010/06/22/keeping-your-sharepoint-2010-development-databases-small/</link>
		<comments>http://blog.hompus.nl/2010/06/22/keeping-your-sharepoint-2010-development-databases-small/#comments</comments>
		<pubDate>Tue, 22 Jun 2010 13:55:40 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SQL]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[Shrink]]></category>
		<category><![CDATA[SQL 2008]]></category>
		<category><![CDATA[Transaction Log]]></category>
		<category><![CDATA[TSQL]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/?p=186</guid>
		<description><![CDATA[With SharePoint 2010 the amount of databases on your SQL server has grown quite a bit. By default most of these databases have their recovery model set to 'FULL'. After some time you will discover you're running out of space.]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/06/22/keeping-your-sharepoint-2010-development-databases-small/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using the people picker over a one-way trust</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/</link>
		<comments>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comments</comments>
		<pubDate>Tue, 01 Jun 2010 14:04:56 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[People Picker]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[SharePoint Foundation]]></category>
		<category><![CDATA[WSS]]></category>
		<category><![CDATA[WSS 3.0]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/</guid>
		<description><![CDATA[When you have a SharePoint farm and you want to use accounts from another domain you need a partial (one-way) or a full (two-way) trust between those domain.

A full trust is not always desirable and there your problem begins. After setting up the one-way trust you can authenticate with an account from the trusted domain, but the SharePoint People Picker doesn't show any accounts from this domain. 

It has been documented by others before, but as I ran into this recently I'll give my summary how I fixed this.

This solution is the same for WSS 3.0/SharePoint 2007 as SharePoint 2010.]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Microsoft extends support for WSS 3.0, SharePoint 2007 and Project Server SP1</title>
		<link>http://blog.hompus.nl/2010/03/24/microsoft-extends-support-for-wss-3-0-sharepoint-2007-and-project-server-sp1/</link>
		<comments>http://blog.hompus.nl/2010/03/24/microsoft-extends-support-for-wss-3-0-sharepoint-2007-and-project-server-sp1/#comments</comments>
		<pubDate>Wed, 24 Mar 2010 16:44:40 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[Project Server]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[Project Server 2007]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[SP1]]></category>
		<category><![CDATA[Support]]></category>
		<category><![CDATA[WSS]]></category>
		<category><![CDATA[WSS 3.0]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2010/03/24/microsoft-extends-support-for-wss-3-0-sharepoint-2007-and-project-server-sp1/</guid>
		<description><![CDATA[Today the news broke Microsoft has extended the support for installations of Windows SharePoint Services 3.0 SP1, Microsoft Office SharePoint Server 2007 SP1 and Project Server 2007 SP1.]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/03/24/microsoft-extends-support-for-wss-3-0-sharepoint-2007-and-project-server-sp1/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Prevent hardcoded SharePoint ID&#8217;s in your code</title>
		<link>http://blog.hompus.nl/2010/02/05/prevent-hardcoded-sharepoint-ids-in-your-code/</link>
		<comments>http://blog.hompus.nl/2010/02/05/prevent-hardcoded-sharepoint-ids-in-your-code/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 11:44:39 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[ContentType]]></category>
		<category><![CDATA[Feature]]></category>
		<category><![CDATA[Field]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[User Profile]]></category>
		<category><![CDATA[WSS]]></category>
		<category><![CDATA[WSS 3.0]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2010/02/05/prevent-hardcoded-sharepoint-ids-in-your-code/</guid>
		<description><![CDATA[Now and again I come across code with hardcoded SharePoint ID&#8217;s in it. Or scary loops matching a field, list or property name. SharePoint provides some classes containing the out of the box ID&#8217;s, you only have to know they exist. I made an overview so nobody has to hardcode those pesky GUID&#8217;s, ContentTypeId&#8217;s or [...]]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/02/05/prevent-hardcoded-sharepoint-ids-in-your-code/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Calling a SharePoint Web Service from Silverlight over HTTP and HTTPS</title>
		<link>http://blog.hompus.nl/2010/01/27/calling-a-sharepoint-web-service-from-silverlight-over-http-and-https/</link>
		<comments>http://blog.hompus.nl/2010/01/27/calling-a-sharepoint-web-service-from-silverlight-over-http-and-https/#comments</comments>
		<pubDate>Wed, 27 Jan 2010 10:52:58 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[C#]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[BasicHttpBinding]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[HTTPS]]></category>
		<category><![CDATA[Query]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[Silverlight]]></category>
		<category><![CDATA[WCF]]></category>
		<category><![CDATA[Web Service]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2010/01/27/calling-a-sharepoint-web-service-from-silverlight-over-http-and-https/</guid>
		<description><![CDATA[The past couple of weeks I&#8217;m working with Silverlight controls embedded in SharePoint 2007. For one of the controls I need to retrieve the data using the Search Query Web Service. I was using the following code: private void Page_Loaded(object sender, RoutedEventArgs e) { var endpoint = new EndpointAddress(GetParam(&#34;SharePointWeb&#34;) + &#34;/_vti_bin/search.asmx&#34;); var binding = new [...]]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/01/27/calling-a-sharepoint-web-service-from-silverlight-over-http-and-https/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>MySitePublicWebPartPage throws NullReferenceException with August Cumulative Update</title>
		<link>http://blog.hompus.nl/2010/01/15/mysitepublicwebpartpage-throws-nullreferenceexception-with-august-cumulative-update/</link>
		<comments>http://blog.hompus.nl/2010/01/15/mysitepublicwebpartpage-throws-nullreferenceexception-with-august-cumulative-update/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 12:27:31 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[August Update]]></category>
		<category><![CDATA[MOSS]]></category>
		<category><![CDATA[MySite]]></category>
		<category><![CDATA[MySitePublicWebPartPage]]></category>
		<category><![CDATA[NullReferenceException]]></category>
		<category><![CDATA[ProfilePropertyImage]]></category>
		<category><![CDATA[SharePoint 2007]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2010/01/15/mysitepublicwebpartpage-throws-nullreferenceexception-with-august-cumulative-update/</guid>
		<description><![CDATA[The problem With the introduction of the August Cumulative Update for SharePoint 2007 (KB973399) we encountered &#34;System.NullReferenceException: Object reference not set to an instance of an object.&#34; on all pages inheriting from MySitePublicWebPartPage. As can be seen in the stack trace the error occurs from a call by the ProfilePropertyImage control which is on the [...]]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/01/15/mysitepublicwebpartpage-throws-nullreferenceexception-with-august-cumulative-update/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WSS 3.0, SharePoint 2007 and Project Server SP1 support ends soon</title>
		<link>http://blog.hompus.nl/2010/01/11/wss-3-0-sharepoint-2007-and-project-server-sp1-support-ends-soon/</link>
		<comments>http://blog.hompus.nl/2010/01/11/wss-3-0-sharepoint-2007-and-project-server-sp1-support-ends-soon/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 16:26:39 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[Project Server]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[Project Server 2007]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[SP1]]></category>
		<category><![CDATA[SP2]]></category>
		<category><![CDATA[Support]]></category>
		<category><![CDATA[WSS]]></category>
		<category><![CDATA[WSS 3.0]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2010/01/11/wss-3-0-sharepoint-2007-and-project-server-sp1-support-ends-soon/</guid>
		<description><![CDATA[Update March 24th, 2010: Microsoft extends support for WSS 3.0, SharePoint 2007 and Project Server SP1 &#160; Stefan Goßner reminds us of the fact that support for WSS 3.0 SP1, SharePoint 2007 SP1 and Project Server SP1 will soon end. Support ends when the next service pack is out for over a year. And SP2 [...]]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/01/11/wss-3-0-sharepoint-2007-and-project-server-sp1-support-ends-soon/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>MOSS 2007 &#8211; C# Protocol Handler errors fixed</title>
		<link>http://blog.hompus.nl/2009/07/09/moss_2007_-_c_protocol_handler_errors_fixed/</link>
		<comments>http://blog.hompus.nl/2009/07/09/moss_2007_-_c_protocol_handler_errors_fixed/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 18:44:24 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[CodePlex]]></category>
		<category><![CDATA[MOSS]]></category>
		<category><![CDATA[Protocol Handler]]></category>
		<category><![CDATA[SharePoint 2007]]></category>

		<guid isPermaLink="false">http://hompus.wordpress.com/?p=22</guid>
		<description><![CDATA[On CodePlex you can find the MOSS 2007 - C# Protocol Handler project. When working with the code I discovered 2 issues which I both fixed. Both solutions are summarized here.]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2009/07/09/moss_2007_-_c_protocol_handler_errors_fixed/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SharePoint Incremental Crawl takes much longer after adding or removing a user</title>
		<link>http://blog.hompus.nl/2009/03/23/sharepoint_incremental_crawl_takes_much_longer_after_adding_or_removing_a_user/</link>
		<comments>http://blog.hompus.nl/2009/03/23/sharepoint_incremental_crawl_takes_much_longer_after_adding_or_removing_a_user/#comments</comments>
		<pubDate>Mon, 23 Mar 2009 07:15:38 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[ACL]]></category>
		<category><![CDATA[Crawl]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[SharePoint 2007]]></category>

		<guid isPermaLink="false">http://hompus.wordpress.com/2009/03/23/sharepoint_incremental_crawl_takes_much_longer_after_adding_or_removing_a_user/</guid>
		<description><![CDATA[It&#8217;s a sad and known fact that having lot&#8217;s of ACL&#8217;s in your SharePoint database has a negative effect on the performance of your site. What I didn&#8217;t know yet was that changes to the ACL will impact you incremental crawls. Vikram Lakhotia has posted a description about this in his blogpost: &#8220;Sharepoint Incremental Crawl [...]]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2009/03/23/sharepoint_incremental_crawl_takes_much_longer_after_adding_or_removing_a_user/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Access Denied when crawling mysite / people on localhost with a different hostname</title>
		<link>http://blog.hompus.nl/2009/03/12/access_denied_when_crawling_mysite_people_on_localhost_with_a_different_hostname/</link>
		<comments>http://blog.hompus.nl/2009/03/12/access_denied_when_crawling_mysite_people_on_localhost_with_a_different_hostname/#comments</comments>
		<pubDate>Thu, 12 Mar 2009 21:55:34 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[Access denied]]></category>
		<category><![CDATA[Crawl]]></category>
		<category><![CDATA[Local loopback]]></category>
		<category><![CDATA[MySite]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[SharePoint 2007]]></category>

		<guid isPermaLink="false">http://hompus.wordpress.com/2009/03/12/access_denied_when_crawling_mysite_people_on_localhost_with_a_different_hostname/</guid>
		<description><![CDATA[I have a clean install on the latest and greatest: Windows Server 2008, SQL Server 2008 and MOSS 2007 SP1 with all updates. This is the layout of my farm: http://&#60;server&#62;:80 &#8211; Portal http://&#60;server&#62;:8000 &#8211; Central Admin http://&#60;server&#62;:8001 &#8211; SSP http://mysite &#8211; MySites Everything works fine, except the search crawl gave Access Denied errors on [...]]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2009/03/12/access_denied_when_crawling_mysite_people_on_localhost_with_a_different_hostname/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
