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)

Introducing Office Developer Patterns and Practices

Ever since SharePoint Portal Server 2001 was released at the start of the millennium, developers and businesses have tried all types of approaches to customize and bend SharePoint, one way or another.

SharePoint, after a default installation (which in itself is a discussion for a whole other book!), is referred to as an Out-of-Box (OOB) SharePoint. In its history of 15 years of releases for on-premises versions, and more than 5 years of updates with SharePoint Online, developers have always found ways to modify, change, or even remove built-in SharePoint functionality. This could be because of business requirements, usability reasons, or simply that a developer feels that he or she can implement a better implementation of a SharePoint feature.

This has resulted in numerous issues and headaches for both Microsoft, ISVs, Microsoft partner companies trying to make a living providing SharePoint-based solutions, businesses and their IT departments...