SharePoint Thoughts

motion10 SharePoint Twitter Status Notes Control

erwinkoens — Mon, 31 Jan 2011 19:25:38 +0000

The motion10 SharePoint Twitter Status Notes Control is a study project that extends the default status notes control of SharePoint. The study project tried to proof to send the status text to other social media while the default SharePoint status update functionality stays the same. The study project sends the status message to Twitter, but now it’s easy to create code that sends messages to other social media, like LinkedIn, Yammer or Facebook.

: motion10 SharePoint Twitter Status Notes Control

The project is available at CodePlex. The project contains the following elements:

Hammock for Rest – for communication and authentication (OAuth) with Twitter.
Diplo.Twitter - C# Library for easy authentication and sending the status update.

The Diplo.Twitter C# Library is extended to save and load Twitter Credentials from SharePoint User Profile Service Application.

A feature that will create two persisted objects > the Twitter Consumer Keys.
A feature that will register a delegate control.
A delegate control that loads a JavaScript file and C# methods to authenticate and route the twitter message.

When the delegate control is loaded, the OnOnit method will check if the Twitter credentials are known in the Secure Store. If not then the connect button is shown. When the user hits te connect button, the user will be redirected to authenticate at Twitter. After that the user is redirected back and the Token and TokenSecret are saved in the Secure Store. After that the user is authenticated to send tweets.

View the project at CodePlex.
View the documentation.
Download the SharePoint Solution Package.
Download the Source Code.

SharePoint 2010, the virtual coffee corner

erwinkoens — Mon, 31 Jan 2011 18:39:17 +0000

Summer 2010 I wrote an article for TechNet Magazine about the social features in SharePoint. The article is only in dutch available. You can download the article at this location.

The SharePoint Traffic Light Model

erwinkoens — Thu, 10 Sep 2009 09:53:03 +0000

The customizations of SharePoint are very extensive. Problems can be solved on multiple ways. This broad perspective leads to issues. It is not always clear why that solution is choosen. The communication about the different solutions with customers, partners or collegues is sometimes difficult. It should be better if we talk about the same solution and the impact of that solution should be clear. Therefore is the SharePoint Traffic Light Model.

Traffic Light Model

The SharePoint Traffic Light Model divides the different type of customizations tot the colors of a the traffic light. The model is understanding for everybody. With model you can take responsiblity for the choosen solution. The model will also tell something about the impact.

There is a tension between the orange and red customizations. Its the tension between the possibilities of a standard product and the wish of the customer. With orange customizations it is most of the times possible to make an approach to the customers wish. You bounded to the limits of the standard product features (i.e. dataview of content query web part, site definitions. With red customizations you can realize the wish of the customer.With the model you can explain and take resposibility of the impact and possibilities of the solution.

If you want more information about the model please contact me.
If you have remarks on the model, don’t hesitate to make a comment!

Scope with content source rule

erwinkoens — Thu, 10 Sep 2009 09:34:36 +0000

I’am creating a feature that setups the search settings for a project. The feature creates some content sources and scopes. I discoverd that there is no method for adding a rule type ‘Content Source’ on the Scope. The following create rule methods are availble:

CreateAllContetRyle
CreatePropertyQueryRule
CreateUrlRule

I expected a method like ‘CreateContentSourceRule’, like the user interface offers. Using reflector I dissabled the page page and found out that a new Content Source rule is created using the CreatePropertyQueryRule:

scope.Rules.CreatePropertyQueryRule(ScopeRuleFilterBehavior.Invlude, managedProperties.["ContentSource"], “yourconcentsourcename”);