Multilingual Provisioning Templates with the Office 365 Developer Patterns and Practices Provisioning Engine

Somehow I don't seem to be able to come up with short titles for my posts :-) A much requested feature was the ability to create a multi-language provisioning template. It turned out that the implementation of that wasn't actually that complex, we had much of the plumbing already in place in the engine. The main question we had to ask ourselves was: how do we specify the various values for each language? We looked into embedding the values into the template itself, but in the end we decided to go for proven grounds and go for resource (RESX) files....

A new year, a new job

2016 has come, and I changed jobs. As of today I will work at Rencore, the company behind SPCAF, and I will be responsible for transformation tooling. I entered the live of a consultant in 2001, before that I have been working as an inhouse IT specialist/consultant for almost 9 years, of which 1.5 years as an expatriate in Stockholm, Sweden. Moving into consulting was a huge change for me. From working every day at the same desk, with the same colleagues, I suddenly spent a big part of my day driving my lease car around The Netherlands....

Using an extensibility provider with the PnP Provisioning Engine

When you use the provisioning engine of the PnP Core project, you can provide an extensibility provider in your XML file. In order to use the Apply-SPOProvisioningTemplate cmdlet with an XML file that contains such a reference, it is important that you also load the assembly, otherwise the engine will fail to instantiate your provider and as a result, the provider will not be executed. An extensibility provider is nothing but a simple class: namespace MyCompany.ExtensibilityProviders { public class MainProvider : IProvisioningExtensibilityProvider { public void ProcessRequest(ClientContext ctx, ProvisioningTemplate template, string configurationData) { // do something in your provider } } } In the ProcessRequest method we...

Getting started with the Office 365 Developer Patterns and Practices PowerShell Cmdlets

The OfficeDev PnP Cmdlets are a set of cmdlets specifically designed to provision and modify artifacts in SharePoint Online. In this way they differ a bit from the PowerShell cmdlets provided by Microsoft which are mainly focused on administrative tasks. In this post I will introduce you to the basics of the cmdlets. The cmdlets utilize CSOM behind the scenes, which means that you can run them on any computer that has access to your server over HTTP / HTTPS. Update 2018-03-14: Updated post to reflect latest state Update 2015-08-25: Updated links Update 2015-08-06: If you want to see the cmdlets...

Office 365 Developer Patterns and Practices PowerShell Cmdlets have moved!

In order to prepare for an upcoming split of our PnP GitHub repository (things where simply getting too big amongst others...) we moved the PowerShell cmdlets to their own repo as of today. You can find them at https://github.com/sharepoint/pnp-powershell. See you there!...