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)

Step 3 - Examining the React project structure

Then, start Visual Studio Code, or open a new window if you already have it opened, and open your project's folder. You can, of course, use another editor if you prefer.

Let's examine the project structure:

The web part file and the folder structure is similar but not the same as in the no-framework project. The main difference is that there is a components folder under the src\webparts\reactTodo web part folder. We can see that, in the ReactTodoWebPart.ts file, there is an import statement, which imports the ReactTodo class from components/ReactTodo. Also, if we examine the ReactTodoWebPart class, we can see that in the render function, instead of creating the HTML directly, we are actually creating a React element using the class definition of ReactTodo and then calling ReactDom to render it to the web part's domElement:

Next, we open ReactTodo.tsx from the components subfolder and examine that file:

We can see that the...