Life as a SharePoint Consultant

Federated Search - Twitter

Stef van Hooijdonk — Tue, 29 Nov 2011 09:42:00 GMT

Wanted to share this little sample federated search location with you. Twitter has a search site where you can search for tweets: http://search.twitter.com It also has a atom feed for results: http://search.twitter.com/search.atom?q={searchTerms} SharePoint...(read more)

October 2011 CU for SharePoint 2010

Stef van Hooijdonk — Wed, 02 Nov 2011 16:35:34 GMT

Short version of it: Download SharePoint Foundation 2010 October 2011 CU Download SharePoint Server 2010 October 2011 CU Want to know more? KB 2596508 - SharePoint Foundation 2010 KB 2596505 - SharePoint Server 2010 Updates...(read more)

Office 365 and Exchange 2010 On-premises

Stef van Hooijdonk — Sat, 09 Jul 2011 09:16:00 GMT

One very cool feature for Office 365 has to be the co-existance support with your Exchange 2010 on-premises. There is now a tool available to help you set this up!...(read more)

New SharePoint 2010 Storage recommendations

Stef van Hooijdonk — Sat, 09 Jul 2011 09:13:37 GMT

We have updated our Software boundaries and limits for SharePoint 2010 with SP1 ! View the anouncement on the product group blog : "If this new guidance is followed SharePoint can support up to 4 TB of data in all usage scenarios and has no imposed...(read more)

SharePoint 2010 SP1

Stef van Hooijdonk — Mon, 04 Jul 2011 14:19:27 GMT

So we have released the first Service Pack for SharePoint 2010, both Foundation and Server. You can find all of the details listed here <-- must read this first !!! Update Foundation first: SharePoint Foundation 2010 Service Pack 1 Service Pack...(read more)

Driving SharePoint Adoption

Stef van Hooijdonk — Wed, 22 Jun 2011 08:50:00 GMT

Help is underway for those of us driving adoption of SharePoint. A new site launched: http://iusesharepoint.com/ And with it a SharePoint Adoption Kit "Ah, driving adoption. We know it can be tough to get a team to change its ways. But you don...(read more)

Technet Content on SharePoint 2010 "Best Practices"

Stef van Hooijdonk — Mon, 20 Jun 2011 12:51:00 GMT

Head over to TechNet on some great content on SharePoint 2010 Operational Excellence : And check at the Best Practices Resouce Center for SharePoint 2010 :...(read more)

MOSS 2007 and ADFS

Stef van Hooijdonk — Wed, 18 May 2011 07:10:35 GMT

Found this today, might be usefull for people who are "stuck" on Microsoft Office SharePoint Server 2007 but want to use ADFS2 or Federation. Microsoft Federation Extensions for SharePoint 3.0 Release to Web http://www.microsoft.com/downloads/en...(read more)

Sample code for a Sandboxed Solution for Office 365 using search.asmx with jQuery

Stef van Hooijdonk — Fri, 06 May 2011 12:17:10 GMT

Wanted to create a sample that: Runs on SharePoint 2010 Uses the Search.asmx webservice Can run inside the sandbox Uses jQuery Can run on Office 365 What to create? A webpart that shows all site collections you have access to! Here is the output of the...(read more)

Office 365 Developer Training Kit online

Stef van Hooijdonk — Mon, 02 May 2011 15:38:15 GMT

Just saw this over at the SharePoint Online Developer Resource Center : Office 365 Developer Training Kit Use this online or downloadable training course to help you get started building cloud-based communication and collaboration solutions for Office...(read more)

Announcing the SharePoint Diagnostic Studio

Stef van Hooijdonk — Mon, 02 May 2011 10:47:00 GMT

Bill Baer posted an announcement over at the the sharepoint blog : " In the new version of the SharePoint Administration Toolkit we’ve introduced a new and revised SharePoint Diagnostics Studio that represents a complete departure from previous...(read more)

April 2011 CU for SharePoint 2007 and 2010 has been released

Stef van Hooijdonk — Mon, 02 May 2011 10:04:00 GMT

Read more here: http://blogs.technet.com/b/stefan_gossner/archive/2011/04/27/april-2011-cu-for-sharepoint-2007-and-2010-has-been-released-today.aspx KB 2512783 - WSS 3.0 KB 2512782 - MOSS 2007 KB 2512804 - SharePoint Foundation 2010 ...(read more)

Microsoft SharePoint Online Code Analysis Framework (MSOCAF)

Stef van Hooijdonk — Fri, 01 Apr 2011 12:22:22 GMT

At Microsoft SharePoint Online, as a part of the validation and verification process, a tool is used: MSOCAF.

"MSOCAF analysis executes a set of rules against the custom solutions, prior to submission for deployment approval into the pre-production and production environments. The MSOCAF application is built using an extensible framework so that the SharePoint Online engineering team can add new rules and/or plug-ins in the future. Code analysis within MSOCAF focuses on areas like memory management, security vulnerabilities, exception management, object model usage, quality gates for unsupported features and reporting. The framework leverages existing tools like FxCop, CAT.Net, and SPDisposeCheck to analyze custom solutions. "

Now you can use it yourself too!

MSOCAF

SharePoint 2010 February 2011 CU

Stef van Hooijdonk — Mon, 21 Mar 2011 13:15:00 GMT

The SharePoint 2010 Feburary 2011 CU is available.

MSF2010:
KB2475880: The full server package for Microsoft SharePoint Foundation 2010
Download link

Technorati Tags: SharePoint,SharePoint 2010

SPS2010:
KB2475878: The full server package for SharePoint Server 2010 and contains also the MSF2010 fixes so you need only this one package.
Download link

Important for all Server Applications listed above:
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on all servers in the farm with SharePoint installed. You can run psconfig in parallel on all SharePoint machines.

We have with our February CU also a SharePoint Designer 2010 hotfix package available.

KB2496947: Description of the SharePoint Designer 2010 hotfix package (spd-x-none.msp): February 22, 2011
Download link
Please be sure that you take the right binary version because we have 32bit and 64bit available.

Also available for MOSS 2007 and WSS v3.0: http://blogs.msdn.com/b/joerg_sinemus/archive/2011/02/23/wss-and-moss-february-2011-cu.aspx

Visual Studio 2010 SP1 available (including TFS 2010)

Stef van Hooijdonk — Thu, 10 Mar 2011 13:20:00 GMT

The Visual Studio team have released the first service pack for VS 2010 and TFS 2010.

VS 2010
Visual Studio 2010 Service Pack 1

TFS 2010
Team Foundation Server 2010 Service Pack 1

Why it this SP1 so relevant for SharePoint 2010? We now have .Net Framework 3.5 Unit testing. I'll let you figure this one out ;)
( here is a hint)

Technorati Tags: TFS,SharePoint 2010,TFS 2010

December 2010 CU available for SharePoint 2010 Foundation and Server

Stef van Hooijdonk — Wed, 05 Jan 2011 13:18:00 GMT

Head over here for more details:
http://blogs.technet.com/b/stefan_gossner/archive/2011/01/03/december-2010-cu-for-sharepoint-2007-and-2010-has-been-released-on-friday.aspx

Check the know issues, the server package has 2!

Technorati Tags: SharePoint 2010,SharePoint

Writing your own Trusted Identity provider for SP2010 (3)

Stef van Hooijdonk — Wed, 15 Dec 2010 13:32:00 GMT

This is part three of a Multi Blog post on "writing your own Trusted Identity provider / Claim Provider for SP2010". In the first post I covered:

Create a Custom Security Token Service with the Windows Identity Framework SDK

In the second post I covered:

Create a Custom SPClaimProvider
Register your Custom SPClaimProvider

In this post will:

Create a Trust between your Tusted Identity Provider (STS) and SharePoint 2010
Create or Configure your SP2010 WebApplication to use the Tusted Identity Provider

To create a Trust between your new STS and SharePoint you need to run a few powershell steps:
First we have some variables to set:


$invocation = (Get-Variable MyInvocation -Scope 0).Value
$rootPath = Split-Path $invocation.MyCommand.Path

$spClaimTypesCsv = Join-Path $rootPath "claim-types.csv"

# identity provider certificate
$idpSigningCertificatePath = Join-Path $rootPath "idp-certificate.crt"
# identity provider ca certificate
$idpSigningCertificateAuthority = Join-Path $rootPath "idp-certificate-ca.crt"

# identity provider url and name
$idpPassivEndpoint = "http://stslogin.sp2010.dev/default.aspx"
$idpName = "Verbondsleden"
$idpDisplayName = "Verbondsleden"

# sharepoint webapplication we are going to use to log in to with this identity provider
$spRealm = "http://claims.sp2010.dev/_trust/default.aspx"
# name of the SPClaimProvider in SharePoint we registered earlier
$claimProvider = "VerbondsledenClaimsProvider"
# login/username Claim Type
$userIdentityClaimType = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"

Next we start with the creation of a trust:


Write-Host "Creating signing certificate for {0} from {1}" -f $idpName, $idpSigningCertificatePath
$idpSigningCertificate = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2($idpSigningCertificatePath)
echo $idpSigningCertificate

Write-Host "Trusting the IdP certificate directly {0}" -f $idpSigningCertificatePath
$rootCert = Get-PfxCertificate $idpSigningCertificatePath
Remove-SPTrustedRootAuthority $idpName

#Register the new identity provider
New-SPTrustedRootAuthority $idpName -Certificate $rootCert

This adds a Trust, and you can view this in the Central Administration :

Now we create a SPTrustedIdentityTokenIssuer:


# remove if it already exists
$sts = Get-SPTrustedIdentityTokenIssuer | where {$_.Name -eq $idpName }
if(-not ($sts -eq $null)) {
	"SPTrustedIdentityTokenIssuer {0} already exists, attempting to remove" -f $idpName
    Remove-SPTrustedIdentityTokenIssuer -Identity $idpName
}

# the ClaimTypes the Identity Provider provides, this is not needed because we have a SPClaimProvider
[array] $claimTypeMappings = @()
$spClaimType = Import-Csv $spClaimTypesCsv
foreach ($claimType in $spClaimType) {
	"Adding claim type {0} ({1})" -f $claimType.ClaimType, $claimType.Description
	$claimTypeMapping = New-SPClaimTypeMapping $claimType.ClaimType -IncomingClaimTypeDisplayName $claimType.Name -SameAsIncoming
    if(-not (($claimTypeMapping -eq $null) -or ($claimTypeMapping.InputClaimType -eq $null))) {
        $claimTypeMappings += $claimTypeMapping
    }
}

"Creating SPTrustedIdentityTokenIssuer {0}" -f $idpName
$sts = New-SPTrustedIdentityTokenIssuer -Name $idpName -Description $idpDisplayName -Realm $spRealm -ImportTrustCertificate $idpSigningCertificate -ClaimsMappings $claimTypeMappings -SignInUrl $idpPassivEndpoint -IdentifierClaim $userIdentityClaimType
echo $sts

if($claimProvider -eq "") {
	"Default claim provider selected for {0}" -f $idpName
} else {
	"Setting claim provider for {0} to {1}" -f $idpName, $claimProvider
	Set-SPTrustedIdentityTokenIssuer -Identity $idpName -ClaimProvider $claimProvider
}

And now we can trust our own STS in our Claims Based WebApplication:

Off course there is an App/Wizard for this also: SPFedUtil.

So there you have it, when you browse your Claims Based WebApplicaiton you will now get this screen:

Choose your STS, login with proper credentials, and you will be redirected to your SharePoint WebApplication:

Small Bonus tip: add an identity claim to a Site collection Group


$usr = New-SPClaimsPrincipal -TrustedIdentityTokenIssuer "Verbondsleden" -Identity "user@company.com"
New-SPUser $usr.ToEncodedString() -web http://claims.sp2010.dev
Set-SPUser -Identity $usr.ToEncodedString() -web $url -group "Groupname"
# done

Small Bonus tip 2: add a AD Group to a Site collection group with Claims based authentication:


$grp1 = (New-Object System.Security.Principal.NTAccount("TEST", "domain users")).Translate([System.Security.Principal.SecurityIdentifier]).Value
$memberclaims = New-SPClaimsPrincipal -Identity $grp1 -IdentityType WindowsSecurityGroupSid
New-SPUser  $memberclaims.ToEncodedString() -web http://claims.sp2010.dev
Set-SPUser -Identity $memberclaims.ToEncodedString() -web $url -group "Groupname"
# done

Writing your own Trusted Identity provider for SP2010 (2)

Stef van Hooijdonk — Wed, 08 Dec 2010 13:29:00 GMT

This is part two of a Multi Blog post on "writing your own Trusted Identity provider / Claim Provider for SP2010".
In the first post I covered:

Create a Custom Security Token Service with the Windows Identity Framework SDK

In this post I will cover:

Create a Custom SPClaimProvider
Register your Custom SPClaimProvider

Create a Custom SPClaimProvider

For SharePoint 2010 to Trust any Identity Provider, we need a SPClaimProvider specific for that provider. This SPClaimProvider has two main purposes:

Provide a way for SharePoint to communicate with any Trusted Identity Provider in a uniform (Interface) way.
And provide SharePoint a way to use the same Claims for Users that have logged in through a different (e.g. AD) Identity Provider, let's call this Claims Augmentation

To create a SPClaimProvider follow the following steps:

Create a new VS2010 Empty SP2010 Project
And add references to Microsoft.IdentityModel, Microsoft.SharePoint and Microsoft.SharePoint.Security.
Create a new Class, let's name it CustomClaimsProvider and inherit from:Microsoft.SharePoint.Administration.Claims.SPClaimProvider
Implement all the methods for resolving claims, this is so we can use the claims provided within SharePoint to give rights to claims:
- FillHierarchy
- FillResolve
- FillSearch, FillSchema
- FillClaimTypes,FillClaimValueTypes,FillEntityTypes
Implement FillClaimsForEntity for the claims augmentation
Override the SupportsEntityInformation,SupportsHierarchy,,SupportsResolve and SupportsSearch properties and let them "return True" since we have implemented all the Fill Methods for this SPClaimProvider
Give your Provider a Name by overriding the Property Name. You will need this later on.

In fairness, this post has an excellent description on the subject also.
Sample implementation of FillClaimsForEntity

 1: /// <summary>

 2: /// Get's the username part of a claims authentication login claim

 3: /// figure out who the user is so we know what team to add to their claim

 4: /// the entity.Value from the input parameter contains the name of the

 5: /// authenticated user. for a SQL FBA user, it looks something like

 6: /// 0#.f|sqlmembership|user1; for a Windows claims user it looks something

 7: /// 0#.w|steve\\wilmaf

 8: /// 0#.t|Customsleden|stef@tamtam.nl

 9: /// </summary>

 10: /// <param name="identityClaims"></param>

 11: /// <returns>only the login part</returns>

 12: public static string GetLoginPartFromIdentityClaim(string identityClaims) {

 13:     string login = identityClaims;

 14:     if (!string.IsNullOrEmpty(login) && login.Contains("|")) {

 15:         string[] parts = login.Split('|');

 16:         if (parts.GetLength(0) == 3) // formsbased or trusted provider based

 17:             login = parts[2];

 18:         if (parts.GetLength(0) == 2) // windows based

 19:             login = parts[1];

 20:     }

 21:     return login;

 22: }

23:

 24: /// <summary>

 25: /// Add Claims to a logged in User, from Dynamics CRM info

 26: /// </summary>

 27: /// <param name="context">Current Context, url</param>

 28: /// <param name="entity">the logged in user/claim</param>

 29: /// <param name="claims">The list of claims for the user</param>

 30: protected override void FillClaimsForEntity(Uri context, SPClaim entity, List<SPClaim> claims) {

 31:     if (claims == null)

 32:         throw new ArgumentNullException("claims");

 33:     if (entity == null)

 34:         throw new ArgumentNullException("entity");

35:

 36:     Logging.LogMessage(entity.Value);

37:

 38:     string login = Utilities.GetLoginPartFromIdentityClaim(entity.Value);

39:

 40:     // if windows user, get the email ?

 41:     if (!string.IsNullOrEmpty(login)) {

 42:         Logging.LogMessage(string.Format("User is {0}", login));

43:

 44:         CRMClient.Entities.User user = null;

 45:         string email = login;

 46:         if (login.Contains("@")) {

 47:             user = CRMClient.CrmSQLClient.GetUserByEmail(login);

 48:         }

 49:         if (login.Contains("\\")) {

 50:             user = CRMClient.CrmSQLClient.GetUser(login);

 51:             if (user != null)

 52:                 email = user.Email;

 53:         }

 54:         // employee, crm users

 55:         if (user != null) {

 56:             try {

 57:                 Logging.LogMessage(string.Format("User is SystemUser of CRM with an license, Name:{0}", user.FullName));

58:

 59:                 claims.Add( GetClaim(CustomClaimsProvider.CustomAccountTypeClaimType, "everyone"));

60:

 61:                 SPClaim employee = null;

 62:                 if (user.FullLicense) { // admin and or full license

 63:                     employee = GetClaim(CustomClaimsProvider.CustomAccountTypeClaimType, "employee");

 64:                 }

 65:                 else {// readonly

 66:                     employee = GetClaim(CustomClaimsProvider.CustomAccountTypeClaimType, "employeero");

 67:                 }

 68:                 if (employee != null)

 69:                     claims.Add(employee);

 70:             }

 71:             catch (Exception exc) {

 72:                 Logging.LogException(exc);

 73:             }

 74:         }

 75:         else {

 76:             Logging.LogMessage(string.Format("{0} not found as SYSTEMUSER in CRM", login));

 77:         }

 78:     }

 79: }

Register your Claims Provider for SharePoint

In order for your Claims Provider to be registered within SharePoint 2010 you will need to create a specific type of Feature.

Add a Farm Feature to your Project
Add an EventReicever to your new Feature
And let your receiver inherit from SPClaimProviderFeatureReceiver (see: Register)
And now implement the following Properties in your Feature Event Receiver
- ClaimProviderDisplayName
- ClaimProviderDescription
- ClaimProviderAssembly
- ClaimProviderType

You can use this to return the last two properties:

 1: /// <summary>Get the Full Assembly Name of the Claim provider we want to register</summary>

 2: public override string ClaimProviderAssembly {

 3:     get {

 4:         return typeof(CustomClaimsProvider).Assembly.FullName;

 5:     }

 6: }

7:

 8: /// <summary>Get the Class Type of the Claim provider we want to register</summary>

 9: public override string ClaimProviderType {

 10:     get {

 11:         return typeof(CustomClaimsProvider).FullName;

 12:     }

 13: }

That's it, you can now register your Claims Provider, and if you want you can use this as is.
Next post will be on these subjects:

Create a Trust between your Tusted Identity Provider (STS) and SharePoint 2010
Create or Configure your SP2010 WebApplication to use the Tusted Identity Provider

Writing your own Trusted Identity provider for SP2010 (1)

Stef van Hooijdonk — Wed, 01 Dec 2010 13:28:00 GMT

With the introduction of the Windows Identity Framework and SharePoint 2010 it is now possible to have multiple authentication providers on a Single URL on a SPWebApplication.
Especialy in an Extranet scenario this is very usefull:

Employees login with their AD Account
Partners, suppliers, customers login through a (Custom) Trusted Identity Provider ( Like facebook,OpenID or custom )

Image you have a CRM Application (like Microsoft Dynamics CRM 4) where you store all the relations (contacts) your company has with customers, partners and suppliers. You can use this information, e.g. the email addresses and a custom field for a password, to create your own Identity Provider and provide access to your extranet/collaboration portal based on the information stored in the CRM application.

In 2007 you would extend your SPWebApplication and configure Forms Based Authentication. You would lose the Client Integration Features of Office (2007), and you needed to configure your Membership Provider in the Web.Config.

In 2010 we can use a Identity provider/Claim Provider. There are some major differences / benefits in comparison to a custom Membership Provider. With an Identity Provider ( custom or not ):

You can use the Integration Features of the Office (2010) Client
All users connect on the same url / WebApplication
You can re-use a Identity Provider on more than one WebApp (it's now just a Trust thing)
You have Single Sing On (SSO) for free with other WebApps that Trust the same Identity Provider
Configuration is done through PowerShell on all servers at once!

This will be a Multi Blog post on "writing your own Trusted Identity provider / Claim Provider for SP2010".
In order to have a working Trusted Identity provider for SharePoint you will need to do a couple of things:

Create a Custom Security Token Service with the Windows Identity Framework SDK
Create a Custom SPClaimProvider ( see part 2 )
Register your Custom SPClaimProvider ( see part 2 )
Create a Trust between your Tusted Identity Provider (STS) and SharePoint 2010
Create or Configure your SP2010 WebApplication to use the Tusted Identity Provider

This post will focus on how to create a Custom Security Token Service with the Windows Identity Framework SDK.

Download and install Windows Identity Framework SDK for .Net 4.0 ( and thus VS 2010 )
SP2010 runs on .Net 3.5 but since this is a Separate IIS WebApplication you use the 4.0
Create a new Web Project with VS2010 based on the ASP.Net Security Token Service Web Site template

This will be the Website used by users to actually login to
Note the following important classes/methods in the project:
- CustomSecurityTokenService.cs, and especially the method: GetOutputClaimsIdentity
- Login.aspx, and especially the CodeBehind: Page_Load
- Web.Config, and especially the appSettings: IssuerName and SigningCertificateName

Implement the method GetOutputClaimsIdentity,
here I have chosen to login with the user's email address.

   1: /// <summary>This method returns the claims to be issued in the token.</summary>

   2: /// <param name="principal">The caller's principal.</param>

   3: /// <param name="request">The incoming RST, can be

   4: /// used to obtain addtional information.</param>

   5: /// <param name="scope">The scope information

   6: /// corresponding to this request.</param>

   7: /// <exception cref="ArgumentNullException">If 'principal'

   8: /// parameter is null.</exception>

   9: /// <returns>The outgoing claimsIdentity to be included

  10: /// in the issued token.</returns>

  11: protected override IClaimsIdentity GetOutputClaimsIdentity(IClaimsPrincipal principal,

  12:                                         RequestSecurityToken request,

  13:                                         Scope scope) {

  14:     if (null == principal) {

  15:         throw new ArgumentNullException("principal");

  16:     }

  17:     // name = the email address of the user

  18:     string name = principal.Identity.Name;

  19:     // create the new identity

  20:     ClaimsIdentity outputIdentity = new ClaimsIdentity();

  21:     // add new claim based on login/email

  22:     outputIdentity.Claims.Add(new Claim(

  23:       System.IdentityModel.Claims.ClaimTypes.Email,

  24:       principal.Identity.Name));

  25:     // return the claim

  26:     return outputIdentity;

  27: }

If you want to add more claims you can! You could add claims to the output here to facilitate groups of users.

Implement the Login button/event in the Login page

   1: /// <summary>Handle the Page Load</summary>

   2: /// <param name="sender"></param>

   3: /// <param name="e"></param>

   4: protected void Page_Load(object sender, EventArgs e) {

   5:     // Note: Add code to validate user name, password. This code is for illustrative purpose only.

   6:     // Do not use it in production environment.

   7:     if (!string.IsNullOrEmpty(txtUserName.Text)) {

   8:         // Check credentials agains backoffice (Dynamics CRM 4 in this case)

   9:         if (CrmSQLClient.ValidateContactLogin(txtUserName.Text, txtPassword.Text)){

  10:             // Login info is valid, redirect the user.

  11:             if (Request.QueryString["ReturnUrl"] != null) {

  12:                 FormsAuthentication.RedirectFromLoginPage(txtUserName.Text, false);

  13:             }

  14:             else {

  15:                 FormsAuthentication.SetAuthCookie(txtUserName.Text, false);

  16:                 Response.Redirect("default.aspx");

  17:             }

  18:         }

  19:     }

  20: }

Change the login page front end
Add extra functions like "Forgot my password" or "Register for an account" now or later
Deploy your webapplication to IIS.
You should now be able to login to your custom STS with a browser:
Create a proper "FederationMetadata.xml".
This was a bit hard for me at first. But there is an App for that!
- Provide the proper values for the WS-Federation Metadata Generator
- You will need a Certificate to sign the "FederationMetadata.xml" document
- Copy the new "FederationMetadata.xml" to your published STS Website
Test your new STS WebApplication by logging in. You might get an error when you first test this. Use this url to test if your login page works:http://test-server/default.aspx?&wa=wsignin1.0
There is one thing left to do when you want to use your Identity Provider: install a certificate on the Web Server, and use that to sign the FederationMetadata.xml and update the Web.Config of your provider to reference this certificate in the IssuerName.

Next post will descibe the SPClaimProvider to create and register.

And be sure to check-out some small "issues" with Claims Based authentication

The Publishing Cache of SP2010 WebApplications

Stef van Hooijdonk — Mon, 11 Oct 2010 12:40:00 GMT

In a recent post I talked about the publishing cache. It turns out this also applies for Classic Authentication WebApplications. (from the original post:) Have a look into your Developer Dashboard to see what is going on; the warning and critical error...(read more)

SP2010 Rest services ListData.svc not working in RTM

Stef van Hooijdonk — Thu, 26 Aug 2010 15:15:00 GMT

If you want to use the ListData.svc / Rest service in the SP2010 RTM you might get this error: Could not load type ‘System.Data.Services.Providers.IDataServiceUpdateProvider’ from assembly ‘System.Data.Services, Version=3.5.0.0, Culture=neutral, PublicKeyToken...(read more)

Provisioning Publishing Pages

Stef van Hooijdonk — Mon, 23 Aug 2010 13:12:00 GMT

On the interweb there seems to be some confusion on how to provision publishing resources through features. Here is what works for SharePoint 2010. First you wil need a Feature scoped for Site (SPSite), put your ContenType module here. And a Feature scoped...(read more)

Enterprise Search query giving FaultException when using an ORDER BY

Stef van Hooijdonk — Fri, 30 Jul 2010 13:27:00 GMT

Ran into this on a project when using the "FullTextSqlQuery" object to query against the Enterprise Search Service of SharePoint 2010. Had a query that included an Order By clause on my own Managed property other than the normal RANK. string...(read more)

Set default Mysite not working with Office 2010 RTM x64

Stef van Hooijdonk — Sun, 21 Mar 2010 16:17:00 GMT

So, you have installed SharePoint 2010 on your server, you have setup Office 2010 on you client ( x64 ) and now you want your SP2010 Memberships to show up in your Office Client Applications. You navigate to your new SP2010 MySite and want to set it as...(read more)

Power of PowerShell and the SharePoint Snap-in

Stef van Hooijdonk — Tue, 02 Mar 2010 16:01:00 GMT

Recently I started to look into some more detail at PowerShell and the SharePoint 2010 Snap-in. As a small exercise I wanted to create something (somewhat) usefull. I came up with a small site structure install script for SP2010. First the source configuration...(read more)