<?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 2010</title>
	<atom:link href="http://blog.hompus.nl/tag/sharepoint-2010/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hompus.nl</link>
	<description>Because I like to share knowledge</description>
	<lastBuildDate>Fri, 11 Mar 2011 13:35:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Translating URLs using Alternate Access Mappings from code</title>
		<link>http://blog.hompus.nl/2011/02/23/translating-urls-using-the-alternate-access-mappings/</link>
		<comments>http://blog.hompus.nl/2011/02/23/translating-urls-using-the-alternate-access-mappings/#comments</comments>
		<pubDate>Wed, 23 Feb 2011 16:48:22 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[AAM]]></category>
		<category><![CDATA[Alternate Access Mapping]]></category>
		<category><![CDATA[SharePoint 2007]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[SharePoint Foundation]]></category>
		<category><![CDATA[URI]]></category>
		<category><![CDATA[WSS]]></category>
		<category><![CDATA[WSS 3.0]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2011/02/23/translating-urls-using-the-alternate-access-mappings/</guid>
		<description><![CDATA[With SharePoint it’s easy to configure multiple zones for your SharePoint Web Application. For example you have a Publishing Web Site with two zones.

The authenticated CMS where editors can mange content: http://cms.int 
The anonymous website where everybody can view the content: http://www.ext 
When the editors link to sites, pages, documents and images the URL will start with http://cms.int. After the content is published it’ll also be available on the anonymous site. Now most of the URLs will be automatically translated to corresponding zone URL and start with http://www.ext.

There are however some place this is not the case. You could try to use relative URLs but even that won’t fix every scenario.]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2011/02/23/translating-urls-using-the-alternate-access-mappings/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Configure people picker over a one-way trust using PowerShell</title>
		<link>http://blog.hompus.nl/2011/01/17/configure-people-picker-over-a-one-way-trust-using-powershell/</link>
		<comments>http://blog.hompus.nl/2011/01/17/configure-people-picker-over-a-one-way-trust-using-powershell/#comments</comments>
		<pubDate>Mon, 17 Jan 2011 18:16:47 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[PowerShell]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[People Picker]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[SharePoint Foundation]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/?p=201</guid>
		<description><![CDATA[In a previous post I have written about Using the people picker over a one-way trust. In this post I use STSADM commands as there are no other ways to configure this. A downside of the STSADM command is your domain password being visible on the command prompt in clear text for everybody to read, or to retrieve from the command line history.

SharePoint 2010 introduces several cmdlets to replace the “old” STSADM commands. Microsoft has posted an overview of the STSADM to Windows PowerShell mapping. However the commands for configuring the people picker are not available.]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2011/01/17/configure-people-picker-over-a-one-way-trust-using-powershell/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<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[SharePoint]]></category>
		<category><![CDATA[SQL]]></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>4</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>8</slash:comments>
		</item>
		<item>
		<title>Could not load type IDataServiceUpdateProvider when using REST with SharePoint 2010</title>
		<link>http://blog.hompus.nl/2010/03/26/could-not-load-type-idataserviceupdateprovider-when-using-rest-with-sharepoint-2010/</link>
		<comments>http://blog.hompus.nl/2010/03/26/could-not-load-type-idataserviceupdateprovider-when-using-rest-with-sharepoint-2010/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 10:00:06 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[ADO.NET]]></category>
		<category><![CDATA[Atom]]></category>
		<category><![CDATA[Data Services]]></category>
		<category><![CDATA[Foundation]]></category>
		<category><![CDATA[OData]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[WCF]]></category>

		<guid isPermaLink="false">http://blog.hompus.nl/2010/03/26/could-not-load-type-idataserviceupdateprovider-when-using-rest-with-sharepoint-2010/</guid>
		<description><![CDATA[I wanted to use the new REST services in SharePoint 2010. 
But when I navigated to the ListData.svc service. I got the following error: "Could not load type 'System.Data.Services.Providers.IDataServiceUpdateProvider' from assembly 'System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'."]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2010/03/26/could-not-load-type-idataserviceupdateprovider-when-using-rest-with-sharepoint-2010/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>SharePoint 2010 and Project Server 2010 System Requirements</title>
		<link>http://blog.hompus.nl/2009/05/12/sharepoint_2010_and_project_server_2010/</link>
		<comments>http://blog.hompus.nl/2009/05/12/sharepoint_2010_and_project_server_2010/#comments</comments>
		<pubDate>Tue, 12 May 2009 01:14:28 +0000</pubDate>
		<dc:creator>Michaël Hompus</dc:creator>
				<category><![CDATA[Project Server]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[Project Server 2010]]></category>
		<category><![CDATA[SharePoint 2010]]></category>
		<category><![CDATA[System requirements]]></category>

		<guid isPermaLink="false">http://hompus.wordpress.com/2009/05/12/sharepoint_2010_and_project_server_2010/</guid>
		<description><![CDATA[As announced yesterday by Microsoft the 2010 product will be 64bit only. Well no surprise there, we already knew that. But they went even further. Because of their experience with customer implementations of the 2007 series they recognize that having Windows Server 2008 and SQL Server on 64bit is a must for ensuring the best [...]]]></description>
		<wfw:commentRss>http://blog.hompus.nl/2009/05/12/sharepoint_2010_and_project_server_2010/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

