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)

Property panes in classic web parts

Classic web parts, and also typically those that have been available in SharePoint Online for a long time, expose a classic property pane. This is readily accessible when you edit a page and hover the mouse over a web part.

In the following screenshot, a Content Editor Web Part has been added on a page, and in order to edit the contents, we need to click on the small down-arrow in the top-right corner:

This forces a page refresh, which also instructs the Content Editor Web Part to display the property pane on the right side of the page:

This has been both cumbersome and also problematic when a page consists of multiple web parts, as the property pane is in a fixed position relative to page contents. In pages with more content, the property pane is fixed in the top-right corner, while the content you're truly working on might be several page lengths lower.

Regardless of its usability, the property pane is very useful and easy to use. Developers...