Rob Garrett – Blog

Triggering custom behavior, after sub-site (web) creation in SharePoint 2007, involved stapling a custom site feature to the site definition. SharePoint 2010 provides additional “web” events, which developers may bind custom event receivers and execute custom code. Creating a new event receiver and binding to web events is a simple exercise in Visual Studio 2010 [...]

Read Full Post »

In the old days of SharePoint 2007, the master page reference in a publishing page layout lived in the MasterPageFile attribute of the @Page reference at the top off the layout file.  This made good when you needed to create a page layout that stood out from the common branding of the site – such [...]

Read Full Post »

I’ve been working lately on a project that requires access to the Managed Metadata Service in SP2010.  I got to a point where I needed to add a term to the default term store under a term set. I have some code in my project that takes in the following parameters and creates a term [...]

Read Full Post »

I recently had to write a feature to provision the SharePoint 2010 Term Store. Numerous blog posts exist on how to populate the term store using Power Shell or how to write XML to add terms to the store, but what I wanted to do was a little different.  The requirements for my feature were [...]

Read Full Post »

I happened to configure my SP2010 farm using Powershell automated scripts and and as a result my default Metadata term store proxy was not default for any new or existing site collections.  This issue manifested itself when I was trying to access the default site collection term store via the SharePoint API as a property [...]

Read Full Post »

This post is to help my my strained memory, the following post contains a list of all SharePoint 2010 feature GUIDs

Read Full Post »

If you see an HTTP 404 when accessing the /_vti_bin/ListData.svc WCF service in SharePoint 2010 then be sure to install the ADO.NET Data Services 1.5 CTP2 Link

Read Full Post »

If you want to make sure that you aren’t using any of the restricted APIs before you deploy your solution to a sandbox environment, manually reference your project against: [SharePoint Root]\UserCode\assemblies\Microsoft.SharePoint.dll   If your code compiles, then you’re pretty safe! NEVER DEPLOY code with this Microsoft.SharePoint.dll reference, instead reference the Microsoft.SharePoint.dll in [SharePoint Root]\ISAPI folder. From the [...]

Read Full Post »