Late last year I published a few Jest presets to simplify adding automated testing to your SharePoint Framework (SPFx) projects. These are complete with example tests including testing the rendering of components, testing async functions using promises or callbacks and even simulating user events. You can learn more about the presets in the original post, Enable Jest testing of SharePoint Framework Projects in One Simple Step. In this post, I want to share some updates to the presets that have been published.

When I’m teaching React to developers, one thing that comes up often is dealing with a common error. But here’s the interesting thing: it’s not running into the error that comes up all the time, its how to deal with it that surprises them. I’ve always wanted to have something to point to that the scenario & why one option is better than others, even though there are plenty of ways to address the issue. That’s what this post is!

A few weeks ago I posted that I am going to be in Prague in early December for ESPC 2019 speaking on SharePoint Framework development.

In just four simple steps, this post will show you how to automate the build, test & deployment to SharePoint Online of any SharePoint Framework project using Azure Pipelines.

I originally intended to write this post a mid-summer, but just never happened. Thankfully my wish list hasn’t changed for the SharePoint Framework (SFPx) since the spring of this year… wait, maybe that isn’t a good thing? Please don’t take these as complaints about the SharePoint Framework, the people who work on it and support it, or Microsoft as a whole. I’m a fan of the SharePoint Framework. I love how it is helping to bring traditional server-side SharePoint developers along to the modern world of web development and client-side customizations. So many parts of the toolchain and skills they are learning by working with SPFx are immediately transferrable to non-SharePoint projects. As you read through my list, you may notice a theme: time for some maturity. The SharePoint Framework has been available since early 2017 and every few weeks, we see Microsoft share graphs of constant growth in adoption during the community calls). With some strong momentum, personally I’d like to see Microsoft slow things down, hold a bug bash & focus on reliability.

In just a few days, from September 10-12, 2019, the folks at Collab365 are putting on a FREE ONLINE SharePoint Summit! This event spans a few days and consists of quite a few presentations by SharePoint professionals all over the world. You’ll find dev content, IT Pro content and adoption content!

In December later this year, I will be at the European SharePoint, Office 365 & Azure Conference in Prague presenting topics on the SharePoint Framework SharePoint developers. This is my second time with ESPC after joining the show in Copenhagen in December 2018. I’m very much looking forward to this year’s event, just like last year’s conference. It will be my first trip to Prague, a city I’m really looking forward to explore when time allows.

Last week I wrote how I migrated my site from a dynamic CMS to a static site generated using Hugo. The site & all supporting processes are hosted in Microsoft Azure. In this post, I will explain how the site is automatically built and deployed when I either push new/updated content as well as on a scheduled basis. This is all implemented using Azure DevOps pipelines.

Last week I wrote how I migrated my site from a dynamic CMS to a static site generated using Hugo. The entire site and all supporting processes are hosted in the Microsoft cloud, specifically Azure DevOps & Microsoft Azure. In this post, I will explain how the site is hosted in Microsoft Azure. This assumes the static files have already been built so you will see how it's exposed to the world.

I started this site and blogging as a personal journal almost exactly 16 years ago today, in September 2003. Over the last 16 years, I’ve used three different open source engines to implement the site, starting with .Text, it’s successor SubText and then moved to Orchard CMS in 2013. Orchard served me well for the last six years, but after much consideration, I’ve made yet another re-platforming move. The site you’re reading right now is on the new platform!