Office Development MVP / Office 365 & Azure Development

 

This week I needed to extend the search core result web part to be able to do some custom filtering and search result styling. For the search result styling, additional fetched properties (columns) needed to be added programmatically to the Web Part properties. But every time I checked in the web part properties, these fetched properties were not added, and I end up with the default fetched properties.

 

In this blog post I will talk about how to automate the SharePoint solution creation process by making use of NuGet. As an example I will use NuGet to automate the SharePoint Branding process in Visual Studio. NuGet is a package management system for your develop environment. NuGet makes the process of importing .

 

When you need to convert an application page from SharePoint 2010 to SharePoint 2007, these are the steps that need to be done: Change the “SharePoint.WebControls” and the “SharePoint.Utilities” assemblies version numbers from “14.0.0.0” to “12.0.0.0”; Remove the “Microsoft.Web.CommandUI” assembly line: Assembly Reference to be removed Change the “DynamicMasterPageFile” attribute name to “MasterPageFile”, and replace the value with the following: MasterPageFile Attribute The result should be something like this:

 

Today I received my Office 365 account, so I thought it would be cool to check out if my sandbox web part, that I have created some time ago, is working on SharePoint Online. Here is the link to the original blog post: Creating a Sandboxed Visual Web Part from the To-do List

 

Thanks to Katrien De Graeve for giving me the inspiration of this blog post. Last week on the HTML5 Web Camp session in Belgium, she talked about the site pinning functionality of IE9. She also recommended a jQuery plugin called ie9ify that makes site pinning integration much easier. The day after the session I started experimenting with the ie9ify plugin, and it was working as suspected.

 

In SharePoint 2007 you had the ability to quiesce the farm inside central administration. This ability is not implemented in SharePoint 2010, you need to use the STSADM command to achieve this. 1 stsadm -o quiescefarm -maxduration minutes But, I have done some research and development to achieve the same as in SharePoint 2007.