Latest SharePoint Framework (SPFx) topics

This is my first course self-published under my company Voitanos! Choose between three course bundles, including the entirely free STARTER bundle!

I originally intended to write this post mid-summer, but just never happened. Thankfully my wish list hasn’t changed for the SharePoint Framework (SPFx) since the spring of this year… wait, maybe that isn’t a good thing?

In this series, I showed you how to build custom elements, a native web technology supported natively by most browsers (except you Edge & IE…) and presented two options for how you can go about it. One option involves using one big project with the SharePoint Framework & Angular in it while the other utilizes two projects to mitigate the downsides of the one-project approach. So, you can now use Angular in SharePoint Framework projects and this is made possible by Angular Elements which was introduced in Angular v6 back in May 2017. Sweet! We’ve got the “can you do it” question answered! But, should you do it? There are always tradeoffs when picking a web framework for your next project and using one with the SharePoint Framework is no different. Let’s take a step back and look at the whole picture. Only then can you decide if it makes sense for you.

This has been a long time coming and many of you Angular developers who also work with the SharePoint Framework may have given up by now and switched to React, but for those of you who have been holding out, Angular is finally a viable option for SPFx development even with a few drawbacks.

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.

Microsoft regularly hosts three different community calls under the SharePoint PnP program on various topics. You can learn all about these from the community page in the SharePoint docs at SharePoint Development > Community > Community Calls . These calls are always recorded and published to the SharePoint PnP YouTube channel. However, during the month of July 2019 schedules are getting a bit out of control with various vacations where no one from the Microsoft side can host the calls and start the recordings.

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.md) 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. A new SharePoint Framework Yeoman generator has been published by OfficeDev: 1.

I’m excited to share this latest update to my course, Mastering the SharePoint Framework for developers. This update, packaged as sprint 16, includes one new chapter and a LOT of updates. When I originally planned out sprint 16, I intended to record a lot of new content. However when the SPFx v1.8.0 release came out there were enough changes to SPFx that I decided to go back and update the course, including adding some new lessons, completely re-recording existing lessons and updating quite a few lessons (both video & notes).

This module will introduce you to working with SharePoint content in SharePoint Framework projects. You’ll learn about the SharePoint REST API, do CRUD operations with SharePoint data, the local workbench, and creating mock data in SharePoint Framework.

On Thursday, March 14, 2019, Microsoft released v1.8.0 of the SharePoint Framework (SPFx). This release is packed with many features that were previously in developer preview to the Generally Available (GA) milestone. However, there are some subtle updates that developers have been asking for. In this post, I’ll summarize some of what you can find, but also share some details I found after spending some time with the v1.8.0 release, kicking the tires and finding a few resolutions to issues.

In my last post, Securing an Azure Function App with Microsoft Entra ID - Works with SharePoint Framework!, I showed how you can secure a REST API deployed as an Azure Function App using Microsoft Entra ID. This comes in quite handy when you want to secure some custom server-side business logic that’’s called from a SharePoint Framework (SPFx) client-side solution. The SPFx docs show how to use APIs with permissions to the Microsoft Graph. This post will explain how to add custom permissions to the AzureAD application that is used to secure your Azure Function.

I recently published a new chapter in my Mastering the SharePoint Framework on-demand course for developers that included a section that showed how to call a REST API deployed using an Azure Function App and secured with Microsoft Entra ID from the SharePoint Framework. When I was working on this chapter, it felt like the process of configuring an Azure Function App to be secured with Microsoft Entra ID was harder and more complex than it should have been. Specifically, some of the things you do aren’t explained as well… so I decided to blog about it here!

Developers can declare permissions in SharePoint Framework projects, but it isn’t a good idea. In this article I explain why and suggest a better approach.

I’m excited to share this latest update to my course, Mastering the SharePoint Framework for developers. Today’s update, packaged as sprint 13, includes two new chapters and a few updates… and it’s a huge release… the biggest yet adding over 3 hours of new content! Sprint 13 also marks a milestone: the Fundamentals Bundle of the course is now content complete! This means all planned chapters are now published. I will continue to make edits to existing chapters updating content when circumstances warrant, but at this time no new chapters or lessons are planned.

This module introduces you to using external APIs in your SharePoint Framework projects. SharePoint Framework projects can incorporate data from anonymous APIs, those REST APIs secured with Microsoft Entra ID, and Microsoft Graph.

Setting up projects to use Jest, especially to test the rendering of your ReactJS SharePoint Framework projects & use the popular tool Enzyme for testing rendering, isn’t a trivial task, until now!

You know what I don’t like about automated tests? Most of the time, we don’t automate them, we just instrument them. We write our tests and then open a console window to run them periodically. Maybe we set up a watcher to automatically rerun them when either a test or the code file changes, and maybe we use an integrated console window in our editor to monitor when things change.

The latest version of the SharePoint Framework (SPFx) released a few weeks ago, v1.7.0, uncovered a few issues between how the various Node.js package managers work. These issues appear to be rooted in the package tslint and came about with a change in how Microsoft was using tslint under the covers from SPFx v1.6 to v1.7. A fix has been submitted to tslint, but they appear to be lagging on their release schedule so there’s no ETA on when it will get rolled out.

On November 8, 2018 (last Thursday), Microsoft released v1.7.0 of the SharePoint Framework (SPFx). This release is filled with a lot of new things Microsoft has been talking about for a few months. In this post, I’ll summarize some of what you can find, but also share some disappointments I had after spending some time picking apart v1.7.0. A new @SharePoint Framework Yeoman generator has been published by @OfficeDev: 1.7.0 #SPFx @Office365 !

I’ve seen more and more questions since the folks at npm added an automatic scan for vulnerabilities after every npm install. What’s going on? The npm registry runs a security audit on npm packages. With the release of npm v6, this command is run automatically when you execute an npm install on your project. You can manually run one of these audits by executing the command npm audit (ref: npm-audit docs ).

This month’s update on my Mastering the SharePoint Framework course features the transition from one sprint to the next. Sprint 12 Complete I published the final pieces of Sprint 12 this week. This includes a new chapter in the Ultimate Bundle, new lessons in two Fundamentals Bundle chapters and a bunch of fixes! Want to get the details? Join me on Facebook Live for a sprint release party tomorrow, Thursday, November 1 at 1pm ET to see what’s in sprint 12 & get a sneak peek to what is planned for sprint 13, Black Friday/Cyber Monday deals & more!

This month’s update on my Mastering the SharePoint Framework course features the transition from one sprint to the next. Sprint 11 Complete Earlier this week, I published the final pieces of Sprint 11. Two new chapters, the first chapters in the Ultimate Bundle! I also hosted the first Facebook Live sprint release party this week… if you missed it, you can get access to the recording here: Voitanos @ Facebook Live Automated Testing of SharePoint Framework Solutions This chapter starts with an overview of automated testing for client-side projects.

In my last post, I talked about using Angular Elements in SharePoint Framework projects. That post showed how to do this using a single SharePoint Framework Project. In this post, I show you a much better option that uses two projects.

In my last post, I talked about using Angular Elements in SharePoint Framework projects. When doing this, you have two options on how you will implement this and in this post, I will talk about doing it in one big project that includes everything. In tomorrow’s post, I’ll show you a much better option that uses two projects.

In this post, learn what’s new with our flagship course, Mastering the SharePoint Framework, in Sprint 10, and what’s coming in Sprint 11!

In the past, I’ve written how I prefer Yarn over npm not just for SharePoint Framework (SPFx) projects, but also for all my Node.js based projects that leverage the npm package registry: https://www.npmjs.org . I wrote that post in December 2016 and things have changed quite a bit since then. Last week Microsoft released SPFx v1.5.0 & the associated Yeoman generator that added support for changing the package manager the generator ran after creating the project scaffolding.

Yesterday Microsoft released a new version of the SharePoint Framework (SPFx) generator to version 1.5. I took some time picking apart the update and in this post, I will show you what these changes have in store for you.

Over the last month of May, we’ve seen quite a few announcements from Microsoft with respect to what’s new and coming related to the SharePoint Framework (SPFx). This news has come out in part at the Microsoft Build 2018 conference in Seattle, WA and the SharePoint Conference North America 2018 in Las Vegas. Some of these things are available today while others are coming soon or in the next few months.

Experienced SharePoint developers give their opinions on Microsoft’s new SharePoint Framework, which allows client-side development in SharePoint.

Citing issues with the Office UI Fabric JavaScript project, I advise against its use and recommend exploring alternative options.

Experienced SharePoint developers give their perspective on Microsoft’s SharePoint Framework, which allows for client-side development in SharePoint.

Experienced SharePoint developers share their own thoughts on the SharePoint Framework introduced by Microsoft in 2016 for client-side development.

Learn what’s new in the May 2018 update of our flagship course, Mastering the SharePoint Framework. We added chapters for jQuery & React!

The SharePoint Framework introduced client-side development as a primary option for SharePoint in 2016. Experienced developers share their thoughts.

A few months ago, we partnered up with Rencore on their third annual State of SharePoint and Office 365 customizations survey. The point of this survey was to learn and share how customers were customizing SharePoint & Office 365. Today, continuing our partnership, I’m launching the first annual comprehensive State of SharePoint Development survey. This survey is for developers with the goal of obtaining and sharing the technical state of SharePoint developers around the world.

I just finished sprint 8 of my Mastering the SharePoint Framework course. Join now &get access to the new chapter in the Fundamentals bundle.

Experienced SharePoint developers share their thoughts on Microsoft’s SharePoint Framework, which introduced a client-side development option in 2016.

Microsoft released a new version of the SharePoint Framework (SPFx) v1.4.1. In this post, I explore what’s in this new release!.

Experienced SharePoint developers discuss the SharePoint Framework as a client-side development option for SharePoint introduced by Microsoft in 2016.

Experienced SharePoint developers share their thoughts on Microsoft’s SharePoint Framework, which offers client-side development for SharePoint.

Experienced SharePoint developers share their thoughts on Microsoft’s 2016 SharePoint Framework, which offers client-side development options.

In 2016, Microsoft introduced SharePoint Framework (SPFx) for extensibility and customization in SharePoint. Experienced devs share their thoughts on SPFx.

Learn what’s new in the January 2018 update of our flagship course, Mastering the SharePoint Framework, including two new chapters!

SharePoint Framework introduced in 2016 as a new development model for SharePoint, enabling client-side development. Experienced developers share insights.

Experienced SharePoint developers share their thoughts on the SharePoint Framework, Microsoft’s new extensibility and customization development model.

I’m sitting here with a smile on my face as I sit back in these last few days of 2017, reflecting on the previous year and looking forward to next year. It’s been quite a ride, finally getting Voitanos off the ground and working up production. While the stakes are not comparable, I cannot help but see similarities with my experience this past year and what Tesla has been doing with their Model 3 sedan.

Last week at the European SharePoint Conference 2017 (ESPC) in Dublin, Ireland, Rob Wormald presented on a new tech being added to the core of Angular that I think will make Angular much more approachable and useful to so many developers. Unfortunately, this session wasn’t recorded nor did I have the opportunity to attend due to co-chairing another conference in Orlando at the same time. I am familiar with the topic though as I’ve been assisting the Angular team in understanding SharePoint & the SharePoint Framework (SPFx) over the last few months. Over that time, I’ve become sold on this approach, not just for SPFx, but for Angular as a whole! In this post, I want to explain how this works.

This post is long, LONG overdue. I’ve explained this multiple times over email & in person to SharePoint Framework developers. It’s about time I have something to point to… so here’s my take on the SharePoint Framework + Angular [v2.0 / v4.0 / v+] state of things. Have you tried to build a client-side web part using the SharePoint Framework using something other than ReactJS? Maybe you prefer using Angular over React… I know I do!

Well, I am just about a week away from the pre-release launch of my Mastering the SharePoint Framework developer course. [Last week I wrote about]({{ ref “mastering-the-sharepoint-framework-on-demand-course-pre-release-availability-news-and-a-50-discount” }}) the September 19th release & how the special 1-day only 50% sale will work. If you missed that, not to worry, watch the following video that explains the pre-release as well as the special 1-day sale (exclusive to you, my email subscribers):