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 Online CDN and Microsoft Azure CDN

We could host these assets anywhere that we can be sure that our users will be able to access them, for example, a public website. But best practice is to use a Content Delivery Network or CDN. These are commercial hosting services that ensure that users download files from servers that are physically close to them and have high bandwidth Internet connections. In some cases, for example, popular JavaScript libraries, the user's browser may already have a cached version of the file avoiding the need to download it altogether.

We'll start with the SharePoint Online-based CDN, as it's probably easier to set up for developers, and often a common approach for serving assets.