Latest SharePoint Framework (SPFx) topics

Today marks a big milestone. Sprint 19 is complete and published - it contains the final two chapters published in my Mastering the SharePoint Framework Ultimate bundle!

The first of these chapters, Sharing Code between SharePoint Framework Solutions, explains and demonstrates how to use either SPFx library components or npm packages to share code across SPFx projects. The other chapter, Property Panes for Client-Side Web Parts: Create Property Controls, demonstrates how to create custom property pane controls for web part projects.

Today I published a new chapter to the Ultimate bundle of my Mastering the SharePoint Framework course. This new chapter, DevOps: Monitoring & Telemetry with Azure Application Insights, is immediately available to all existing Ultimate bundle subscribers!

Yesterday I published a new chapter to the Ultimate bundle of my Mastering the SharePoint Framework course. This new chapter, DevOps: CI/CD with GitHub Actions & Azure Pipelines, is immediately available to all existing Ultimate bundle subscribers!

On Wednesday, April 22, I presented the webinar Get Certified! Overview of the MS-600 exam & Microsoft 365 Developer Associate Certification with Rencore & Waldek Mastykarz. Rencore has posted the recording of the webinar as well as a link to the slides if you weren’t able to join us live or you want to re-watch it. Click here to access the recording.

In that webinar I hinted there was more coming - I’m excited to share with you a new webinar series I hosted in May 2020, and all the recordings are available now!

Microsoft released a new certification in November 2019 for Microsoft 365 developers. The Microsoft 365 Certified: Teams Application Developer Associate certification measures developers across five (5) primary workloads in Microsoft 365. Developers must pass a single exam, the MS-600: Building Applications & Solutions with Microsoft 365 Core Services, to achieve this certification.

Andrew Connell, a Microsoft 365 Development MVP, was deeply involved in working with Microsoft as they created the certification, exam, and associated materials. In this webinar, Andrew walks you through behind the Scenes: Making of the MS-600 exam & Microsoft 365 Developer Associate Certification (webinar recording), one of the five workloads the MS-600 exam will test you on. You’ll learn what topics are covered, what you need to focus on, what resources are available to you, and have an opportunity to ask questions. This isn’t an exam prep or some shortcut to pass the exam.

Microsoft released a new certification in November 2019 for Microsoft 365 developers. The Microsoft 365 Certified: Teams Application Developer Associate certification measures developers across five (5) primary workloads in Microsoft 365. Developers must pass a single exam, the MS-600: Building Applications & Solutions with Microsoft 365 Core Services, to achieve this certification.

Andrew Connell, a Microsoft 365 Development MVP, was deeply involved in working with Microsoft as they created the certification, exam, and associated materials. In this webinar, Andrew walks you through Microsoft SharePoint, one of the five workloads the MS-600 exam will test you on. You’ll learn what topics are covered, what you need to focus on, what resources are available to you, and have an opportunity to ask questions. This isn’t an exam prep or some shortcut to pass the exam.

Late last year, Microsoft introduced a new certification for developers working in the Microsoft 365 space. The Microsoft 365 Certified: Teams Application Developer Associate is intended to measure & certify someone can “design, build, test, and maintain applications and solutions that are optimized for the productivity and collaboration needs of organizations using the Microsoft 365 platform”.

In order to achieve this certification, you must pass a single exam: Exam MS-600: Building Applications and Solutions with Microsoft 365 Core Services.

Have you noticed since installing the Yeoman generator for SharePoint, when you add a web part to a new or existing project and specify the “No JavaScript framework” option, you get a web part who’s render() method’s indentation is all messed up like this?

// omitted for brevity...
export default class HelloWorldWebPart extends BaseClientSideWebPart <IHelloWorldWebPartProps> {

  public render(): void {
    this.domElement.innerHTML = `
      <div class="${ styles.helloWorld }">
    <div class="${ styles.container }">
      <div class="${ styles.row }">
        <div class="${ styles.column }">
          <span class="${ styles.title }">Welcome to SharePoint!</span>
  <p class="${ styles.subTitle }">Customize SharePoint experiences using Web Parts.</p>
    <p class="${ styles.description }">${escape(this.properties.description)}</p>
      <a href="https://aka.ms/spfx" class="${ styles.button }">
        <span class="${ styles.label }">Learn more</span>
          </a>
          </div>
          </div>
          </div>
          </div>`;
  }

  protected get dataVersion(): Version {
  return Version.parse('1.0');
}
// omitted for brevity...

This is frustrating, but it’s very easy to fix.

I’ve updated our Azure Pipelines Templates for SharePoint Framework projects earlier today. This release, v1.3.0, includes a few improvements and updates.

These updates are packed into two releases, v1.2 & v1.3. They are broken up so if you aren’t interested in v1.3, you can configure your pipeline to use just the 1.2 release which includes a specific fix / enhancement.

What’s new

The two releases include three updates & two minor changes to the project. If you want to use the latest version of the templates in your pipelines, just reference the repo as you’ve done in the past. This will default to the master branch.

Like previous years, Microsoft delivered a session at the Microsoft Ignite 2019 conference that was essentially the “State of SharePoint Framework”. This session, BRK3071 - SharePoint Framework: What’s new and what’s next, started with a review of what the SharePoint Framework (SPFx) is and where it can be used. The second half of the session covered what’s coming next with SPFx, both in the short & long term. In this post, I’ll recap what was shared and share my thoughts.

Customers can leverage the SharePoint Framework (SPFx) in any of the modern or recent SharePoint versions. This includes SharePoint Online & SharePoint on-premises versions SharePoint Server 2016 & SharePoint Server 2019. To build a SPFx project, you use the Yeoman generator for the SharePoint Framework to create your project and get started. But there seems to be some confusion on which version you should install depending on your target SharePoint environment. Let’s clear this up, once and for all.

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!

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 guarantee you can have it done before your coffee is ready! Seriously… go get the pot going and come back to this post.

DevOps is all the rage these days. Developers throw it in resumes left and right & the recruiters are always searching for someone who can check that box. But what’s funny is like every other hot term these days, people use the term for everything.

Here’s a post that teaches you a technique that you can start leveraging in your SharePoint Framework (SPFx) projects right away! You know those projects where you have certain values you use in development or testing while others that you use in production? This would include things like different account or IDs used for telemetry services, different endpoints to sample or production data that you’re interacting with in your project.

Earlier this week, on Tuesday, May 7, 2019, Microsoft released v1.8.2 of the SharePoint Framework (SPFx). A little over a month ago, I wrote about the v1.8.0 release. Since then we had another minor release (v1.8.1) released on April 16, 2019.

In this post, I’ll summarize what you can find, and share some additional details I found after spending some time picking apart the last two minor releases.

» SharePoint Framework v1.8.2 official Release Notes

Earlier today I recorded an impromptu Facebook Live video for the recent release of sprints 14 & 15 of the SharePoint Framework. Usually, I let people know about these ahead of time but travel the last few weeks has been rough. Add up issues with production targets that were externally influenced by other people’s schedules, attending the Microsoft 2019 Global MVP Summit & a brief business conference in Las Vegas… I didn’t want to wait any longer.