SharePoint Config

The article Granting access via Azure AD App-Only shows how to setup app-only access to SharePoint using an Azure AD app registration with a Certificate. This article will show how to extend this to work with an Octopus Deploy certificate variable and pipeline.

This article contains details of how to take advantage of the new features in TFS 2013 build to automate the packaging of SharePoint 2013 Apps.

The Managed Metadata functionality provided by SharePoint 2010 allows you to centrally manage metadata and keywords. In a previous post I covered how to provision a SharePoint 2010 managed metadata field and add this to a content type and a list definition. In this post I will cover how to add these types of fields to a publishing page layout so that content authors can add metadata and keywords to webpages they create using these layouts.

If there are a large number of content pages this type of tagging can help users find information as these columns can be used… Continue reading Adding Managed Metadata Fields to SharePoint Publishing Pages »

The first part of this two part series discussed some of the problems with provisioning SharePoint 2010 managed metadata fields. This post will cover a robust method of deploying SharePoint 2010 managed metadata columns in a way that avoids common errors and enables the columns to automatically show up in the search refinement panel.

To recap on the previous post we are aiming to avoid the following problems when creating SharePoint 2010 taxonomy fields through features:

1. If you create a list definition that uses this site column you get the error: Failed to get value of the “{0}” column from the “Managed Metadata” field type control. See details in log. Exception message: Invalid field name. {00000000-0000-0000-0000-000000000000}.
2. The managed metadata column does not appear in

I’ve been working with the managed metadata functionality provided in SharePoint 2010 fairly extensively over the past few months. While it is a great feature and works well when used through the UI it has several rough edges that can cause problems when you are deploying features that use managed metadata fields. Some of these have been documented elsewhere but some of these haven’t so this will be the first of two posts covering (1) some of the potential problems using managed metadata (this post), and (2) a robust way of provisioning SharePoint 2010 managed metadata fields.

Public facing SharePoint websites often contain a combination of content that is publicly available, and sensitive content that should only be shown to authenticated users (e.g. personal details like email, address and other account information). While SSL provides a mechanism for delivering the sensitive content over a secure connection it also has a performance overhead. This often results in a requirement to partially secure the site using SSL/HTTPS, but deliver the remainder of the site via HTTP. This is the first in a series of posts that show how you can accomplish this scenario using SharePoint.

I’ve been involved in several public website projects that have involved using MOSS content deployment. While content deployment is easy to set up for simple scenarios, there are a number of things that can trip you up if you have a significantly customised environment. In this post I’ll give details and solutions to on some of the common problems, and general tips on how to make this process run as smoothly as possible. Continue reading MOSS content deployment tips and tricks »