Book Image

SharePoint Development with the SharePoint Framework

By : Jussi Roine, Olli Jääskeläinen
Book Image

SharePoint Development with the SharePoint Framework

By: Jussi Roine, Olli Jääskeläinen

Overview of this book

SharePoint is one of Microsoft's best known web platforms. A loyal audience of developers, IT Pros and power users use it to build line of business solutions. The SharePoint Framework (SPFx) is a great new option for developing SharePoint solutions. Many developers are creating full-trust based solutions or add-in solutions, while also figuring out where and how SPFx fits in the big picture. This book shows you how design, build, deploy and manage SPFx based solutions for SharePoint Online and SharePoint 2016. The book starts by getting you familiar with the basic capabilities of SPFx. After that, we will walk through the tool-chain on how to best create production-ready solutions that can be easily deployed manually or fully automated throughout your target Office 365 tenants. We describe how to configure and use Visual Studio Code, the de facto development environment for SPFx-based solutions. Next, we provide guidance and a solid approach to packaging and deploying your code. We also present a straightforward approach to troubleshooting and debugging your code an environment where business applications run on the client side instead of the server side.
Table of Contents (14 chapters)

Deploying, retracting, and managing solutions

Now that you have your code managed through VSTS or GitHub, you'll need a way to manage your SharePoint Framework customizations in SharePoint. Once again, there are multiple approaches to this task and you're free to choose the one that most fits your own development workflow and experience.

As all the SharePoint Framework solutions are packaged with Gulp to a separate package, it's very easy to move one or more files to SharePoint for testing and deploying to production. Each SharePoint Framework package is a file with the extension .sppkg, and they work distantly, similarly to SharePoint add-ins.

A centralized approach for this would imply you would use the application catalog, which is a special type of SharePoint site that includes the mechanisms for storing add-ins and SharePoint Framework Packages, and then deploying those through your SharePoint via site collections.

You can have multiple solutions in the application...