Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Practical SharePoint Framework (SPFx) Development
  • Table Of Contents Toc
Practical SharePoint Framework (SPFx) Development

Practical SharePoint Framework (SPFx) Development

By : Franck Cornu, Anoop T.
close
close
Practical SharePoint Framework (SPFx) Development

Practical SharePoint Framework (SPFx) Development

By: Franck Cornu, Anoop T.

Overview of this book

The SharePoint Framework (SPFx) has revolutionized how developers create custom solutions for Microsoft 365. Whether you're building Web Parts, extensions, or full-fledged applications, mastering SPFx is essential for delivering modern and scalable SharePoint solutions. Authored by experienced SPFx developers, this book serves as a comprehensive guide to developing with SPFx, offering practical examples, structured guidance, and best practices. You’ll start by understanding the Microsoft SharePoint and Microsoft 365 ecosystem before exploring hands-on development with SPFx. You’ll learn how to create Web Parts, work with the property pane, connect to APIs, deploy solutions, and implement different types of extensions. Additionally, the book covers debugging, testing, and upgrading solutions efficiently. By the end of this book, you’ll be able to confidently build, deploy, and manage SharePoint solutions using SPFx while leveraging community tools and libraries to enhance development efficiency.
Table of Contents (29 chapters)
close
close
Lock Free Chapter
1
Part 1: Getting Started with the SharePoint Framework
6
Part 2: Building Web Parts with the SharePoint Framework
11
Part 3: Building Extensions with the SharePoint Framework
19
Part 4: Going Further with the SharePoint Framework

Understanding the need for virtualization

While developing solutions (be it SPFx or non-SPFx), we might think of developing/running our code in a different environment rather than directly on our local machine. This might be because of several reasons. A couple of them are listed here:

  • We do not want to have a single version of Node.js on our local machine, as different projects might need different versions.
  • The dependencies that are needed for one project might vary from other projects, and there might be a clash of the versions of dependencies. This might be problematic as the versions need to keep changing every time we switch the project we are working on.
  • If we want multiple people working on a project, we want them to get set up quickly for the project so that they can start coding right away and not spend time installing all the dependencies from scratch.

For these reasons, having a separate isolated place to develop solutions would make sense, as these...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Practical SharePoint Framework (SPFx) Development
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon