Development

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

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. Even without this new --package-manager switch introduced in v1.5.0, the SPFx generator had the command line switch --skip-install that we could add, telling it to not run the package install step, thus allowing us to run our own package manager.

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.

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

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. The findings of this survey will then be summarized into a report that provides valuable insights.

Ever wonder how your organization compares with other organizations in the same space? Have you sat at your desk and thought “I wonder if the challenges we are facing are the same as what others in the industry are facing?” Now is your chance to find out! I’m teaming up with Rencore this year to co-host two surveys. State of SharePoint & Office 365 Customizations 2018 Survey In this first survey by Rencore, you can share some information about your organization (anonymously of course) and learn how your organization compares to others in the industry on topics such as:

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

Many developers picking up the SharePoint Framework are coming from a traditional SharePoint development background. Some of these people server-side developers primarily who may have some client-side development experience while others may have been customizing SharePoint using client-side development techniques for a while.

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! While using AngularJS to create SPFx solutions is fairly straightforward, using Angular is a bit more complicated.

In the most recent SharePoint Patterns & Practices - JavaScript Special Interest Group meeting, Microsoft shared some news on the SharePoint Framework. The news fell into three buckets: Recent Updates Update on SPFx Modern UI Extensions SharePoint Framework Engineering Backlog Recent Updates The big news that in the last few weeks Microsoft introduced a new, and often requested, feature for SPFx: **tenant-scoped deployment for SPFx client-side web parts and extensions. This means addins or extensions can be deployed to all sites within your tenant just a single time!

In the recent SharePoint Framework (SPFx) generator updates in v1.1.1, are we starting to see hints of on-prem SPFx support coming soon?

In this post, I’ll explain how to create a self-signed certificate configure Chrome on your macOS to trust it for local development.

Today Microsoft announced new updates coming to the SharePoint Framework ahead of their sessions at the Build Conference. In a blog post, Build integrated user experiences with new capabilities of SharePoint and OneDrive, they talked about four big additions that engineering is working on and will make it into a new developer preview of the SharePoint Framework by the end of May 2017. This week in the Microsoft Cloud Show podcast episode’s special coverage for the Build conference, CJ & AC sat down with Microsoft’s Vesa Juvonen about these new features and more. Check it out in Episode 193 | Vesa Juvonen on New SharePoint Framework Capabilities Announced at Build!

In last week’s SharePoint Framework & JavaScript Special Interest Group meeting, Microsoft’s Vesa Juvonen shared what’s the engineering team at Microsoft is working on and more! Updated SharePoint Framework Yeoman Generator In early April, Microsoft quietly shipped two updates to the Yeoman generator for the SharePoint Framework, @microsoft/generator-sharepoint. The latest version is v1.0.2. The updates were fairly minor… I recently blogged about what you will find in the updates and how I figured out what the updates were as they aren’t well documented: SharePoint Framework Generator Updated to v1.0.2.

In my post, I point out that SharePoint Framework development involves new build tools and Node.js, which traditional developers find interesting.

Did you know the SharePoint team at Microsoft updated the Yeoman generator, @microsoft/generator-sharepoint, twice in the last month? Yeah… I didn’t either until yesterday. The final version was released on February 23, 2017, as version 1.0.0. They then slipped two more updates in early April in quick succession as versions 1.0.1 & 1.0.2. Unfortunately, Microsoft still hasn’t published the repo for the generator or made the homepage for it in the NPMJS registry of any use… just some boilerplate copy… so it’s not easy to figure out what’s changed.

Learn how using a node version manager (NVM) is a fantastic tool for developers who rely on Node.js… including SharePoint Framework (SPFx) developers!

This article is a follow-up to my recent webinar on “Building Client-Side Web Parts with the SharePoint Framework (SPFx)” with Rencore.

Earlier this week I presented a session at the Atlanta SharePoint User Group on Building Client Side Web Parts with the SharePoint Framework. I had my session planned well in advance, out but wanted to build the demos while they were fresh in my head. Last week I was out of work mode with my family relaxing on a beach in Mexico for Spring Break, so I planned to do build my demos yesterday morning, on Sunday. While we were supposed to return home Saturday night, we missed our international connection and got stuck overnight, not making it home until about 12pm EDT Sunday.

Yesterday Microsoft announced that the SharePoint Framework has reached the Generally Available milestone. That means we’re at v1! The development tools have been updated to v1 and the v1 bits are rolling out to Office 365 SharePoint Online tenants now. Microsoft said it will take about a week or so for it to reach all Office 365 tenancies. You can get the details of this update from their wiki page in the main sp-dev-docs repo. So what change from RC0 to GA?

Last week I was in New Orleans presenting at the Nintex InspireX conference on building apps using the microservice approach with containers and Docker. During that week I sat down with Jeremy Thake of Hyperfish to talk about the SharePoint Framework and what it means for end users of SharePoint. During this discussion we discussed: what is the new SharePoint Framework how the SharePoint Framework will effect the SharePoint user experience some tips on how to keep up with the SharePoint Framework You can listen to the whole discussion on the Hypefish podcast.

If you are a SharePoint developer doing any work in SharePoint Online and you have held out on taking a look at the SharePoint Framework, now is a good time to start taking a look. We are currently at the release candidate 0 (RC0) and in the coming weeks, we can expect to see the generally available (GA) release. This release will support client-side web parts as Microsoft wanted to make sure they got that capability perfected… but they won’t stop there!

This article is a follow-up to my recent webinar on “Introducing the SharePoint Framework (SPFx)” with LightningTools I delivered.

Speed up your JavaScript testing in VSCode with Wallaby.js. Wallaby.js automatically runs your tests and see the results without leaving your code files!

In this article, learn how you can debug Node.js projects, written in TypeScript, using VS Code’s native capabilities.

In this post, I explain how I set up my Node.js projects, written in TypeScript. I’ll share how I build to different folders.

I’m presenting at SPTechCon in Boston, demonstrating how to build an Office Add-in for Outlook with Angular 2, using a hands-on approach.

The post explains the fundamentals of Docker and containerization technology, providing an overview from a different perspective

Listen to my interview on the Adventures in Angular podcast, where I discuss using Angular within Office Add-ins and the Office UI Fabric.

Gulp is a task runner that uses JavaScript to glue plugins and create tasks. Unlike MSBuild, it favors code over configuration.

OfficeUIFabric.com, an open-source project for Office UI Fabric samples, is now at v1.0.0 with full release coverage. Pascal Berger contributed typo fixes.

Discover my request for Angular directives for Office UI Fabric and the similarities I’ve observed with other design languages’ directives.

My post about SharePoint not being a Platform, instead it’s a service SharePoint is a Service sparked discussion. In this post is a rebuttal to feedback.

As a developer of Office 365 & SharePoint app, I stress the importance of having a design language. Learn why it is crucial for your Add-ins & web apps.

Office Add-in development is made easy with Visual Studio, but limited to Windows users. Developers can create add-ins and deploy them easily.

As a SharePoint developer for 12 years, I share my thoughts on the current state of SharePoint development, anticipating diverse reactions.

Everyone in tech wants to be a platform, but the appeal is not new. The idea of being a development platform has been around for a while.

At Microsoft Build and Ignite, a Node.js web app demo integrated TypeScript, AzureAD, ADAL, & Office 365 APIs to run on any platform.

The Angular 2.0 announcement in 2014 caused concern about app rewrites. Poor communication was blamed, but a later conference cleared it up.

In this article, I’ll share my updated process for creating self-signed certificates on MacOS and Chrome, along with some helpful tips.

As an app developer, I share my interest in Microsoft Entra ID (formerly Azure AD) & OpenID Connect for app auth. Join my Pluralsight course to learn more.

Blog post discussing three OAuth2 authentication flows supported by Microsoft Entra ID: Authorization Code, Client Credentials, and Implicit Grant.

The authentication dance can be the hardest part of working with Office 365 APIs. Check out the Pluralsight course on authentication and discovery.

Let me walk you through the steps of running Node.js on a Raspberry Pi 2 Model B microcontroller. You can now code in JavaScript instead of Python or Java.

Developers face challenges in creating a consistent user experience for Office 365 and SharePoint development. Varying UX can lead to issues.