Kerberos is a security protocol that has been implemented in windows.

It is something that you need to get to work if you ever have a windows process that wants to perform an action on a users behalf under that users identity.  It is a bit of a pig to configure.  The only clue that you get is that the remote service is accessed using the Unknown User

Here is an article on enabling Kerberos.

Here is a Microsoft article on troubleshooting Kerberos under IIS.

Here is an article on the BDC and authentication.  The BDC is the expensive version of Sharepoint’s datasource abstraction layer (i.e. it can read from a system that supports .net 2 drivers or has a web service interface).

Classic Microsoft Documentation

This is a very typical piece of microsoft documentation.

It contains the call interface, and a trivial example, yet has left the end user to identify the useful information that should be documented.  It appears that most of the MSDN api documentation has been autogenerated from the code.  Which is completely useless when the names give no clue.

I have been looking at using the WF rules engine outside of the WF framework.  This should be easy to do, yet the documentation sucks.  You end up having to hunt around various blogs &c.

Loading data into a Sharepoint page from a webpart file


using System;

using System.Xml;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebPartPages;






                using (SPSite site = new SPSite(“http://mysite:123456/“))


                    using (SPWeb web = site.OpenWeb(“MySubWeb”))


                        SPFile targetPage = web.GetFile(“default.aspx”);


                        SPLimitedWebPartManager webpartManager = targetPage.GetLimitedWebPartManager(



                        string errMsg;


                        // This is the file that can be exported from the webpart

                        XmlTextReader reader = new XmlTextReader(“summary.webpart”);

                        System.Web.UI.WebControls.WebParts.WebPart webPart = webpartManager.ImportWebPart(reader, out errMsg);


                        webpartManager.AddWebPart(webPart, “TopWebPartZone”, 1);







            catch (Exception ex)





Recently I have been experimenting with PowerShell.

I have a need to configure Sharepoint in a repeatable manner and have considered Powershell as a possible means of doing so.

Here is a site that provides basic PowerShell documentation

Here is a site that has 5 useful Sharepoint PowerShell functions.
The code is missing a reference to the assembly but that can easily be fixed.

This is a site that proves a sample script to recycle the app pool – something that you need to do very frequently in sharepoint development.