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)

SharePoint REST APIs

For SharePoint Online, API support is a bit of a mess. On one hand, developers can directly access most REST-based APIs from https://{tenant}.sharepoint.com/_api/, and when they develop solutions, this is often a valid way of directly communicating with SharePoint.

All APIs available through REST are documented at https://dev.office.com, and a more comprehensive walk-through of constructing the API addresses is found at https://dev.office.com/sharepoint/docs/sp-add-ins/get-to-know-the-sharepoint-rest-service.

Figuring out the API locations is quite easy, as they all follow the same patterns. The base address (https://{tenant}.sharepoint.com) is always the same. By adding /_api/, we can then choose what scope of data we will need to access. The available scopes are the site for a site collection and the web for a single SharePoint site. They map directly to the server-side object model naming conventions, where SPSite is the site collection and SPWeb is a single site...