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)

Localizing web part manifest

Our nonlocalized web part manifest (FeedbackWebPart.manifest.json) looks like this:

The language dependent parts have default properties. If you want to translate those parts to other languages, you do it by adding new language-specific properties and values.

There is one problem in the web part manifest. You can't localize the default values for the properties as easily as other values. There are two ways to do it: either you create multiple preconfiguredEntries objects to support multiple languages or you handle default property values in your code using the strings object as you do with the other language dependent text. The problem with multiple preconfiguredEntries objects is that you usually only want to show the web part to the user once, when he or she is adding it to the page.