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)

Overview

There are a few important considerations you face when you start using third-party frameworks and libraries in your SharePoint Framework web parts. First, you must take TypeScript type definitions, which will allow you to use tools like Intellisense, into account and then you need to decide whether you want to load the external dependencies from CDN or you want to bundle them to your web part.

One of the strengths of TypeScript is type definitions, and when you include third-party libraries and frameworks to your project, it is best to go with the libraries that have type definitions available. With the constantly evolving world of modern web development, this will likely give you a headache at some point. There are versions of libraries and libraries with mismatching type definition versions. Also, the version of TypeScript can come into play because SharePoint Framework is using one version of TypeScript and type definitions available to third-party frameworks or libraries...