21 posts · rss

SharePoint Development

Real SharePoint development problems in C#: provisioning, list items, navigation, content types and the API costs nobody warns you about.

This is the broadest thing I write about, and the reason most people end up here. Almost everything on this blog touches SharePoint somewhere: reading list items without melting the API, provisioning sites that survive a retry, moving content types on a list that is already in production, or working out why the portal offers a checkbox that no API exposes.

Most of it is C# rather than PowerShell. That is partly taste and partly the work: when SharePoint sits behind a web app or a background job, you need the same operation to be fast, retryable and testable, and that pushes you toward the client libraries rather than a script.

If you are new here, the narrower topics are where the real detail lives. Start with CSOM performance if something is slow, or provisioning if something is flaky.

Update list to use content type

Nov 10, 2024 · 3 min

Update list to use content type

We've all tried creating a SharePoint list without using Content Types from the start. It seems like the quick solution, but it can lead to challenges later when restructuring the list. This post explains why using Content Types from the beginning is a smart move that can save time and hassle in the long run.