When we start working with SharePoint, it does not take a single minute for us to recognize the capabilities of the web app that we use. These web apps are not just for making the UI attractive, but they are full of capabilities which allows you to improve or enhance the efficiency as well as the capabilities of your SharePoint Environment as well.
While talking about webpart you must have also heard about SharePoint Framework or SPFx along with it. And that’s because SharePoint Framework is a page/model which is used for building customizations or client-side development on the SharePoint platform. The SharePoint Framework or SPFx provides full support for client-side SharePoint development, easy integration with SharePoint data, and extending Microsoft Teams along with the capabilities of integration with third party apps and sites with the help of various web services. With the SharePoint Framework, you can also use modern web technologies and tools in your preferred development environment to build productive experiences and apps that are responsive and mobile-ready.
Going forward in this blog we will have a small introduction with the SharePoint Framework.
What is the SharePoint Framework?
The SharePoint Framework or SPFx is a development model that is currently recommended by Microsoft for the customization and extensibility of the clients SharePoint environment. It is a framework SDK and API contract for developers who want to customize their SharePoint implementations by creating webpart, extensions, application customizers, etc. Now we are going to look into some of the key features of the SharePoint framework or SPFx.
Key features of the SharePoint Framework
Client-side customization framework
But using the Script Editor webpart there are a few downsides as well. First, while you can package your solution so that end users can drop the control onto the page, you cannot easily provide configuration options. Also, the end user can edit the page and modify the script, which can break the web part. Another significant problem is that the Script Editor web part is not marked as "Safe for Scripting". Most self-service site collections (my-sites, team sites, group sites) have a feature known as "NoScript" enabled. Technically, it is the removal of the Add/Customize Pages (ACP) permission in SharePoint. This means that the Script Editor web part will be blocked from executing on these sites.
SharePoint Add-in model
The NoSript implementation creates an iFrame on the SharePoint page where the actual experience resides and executes. A huge advantage of this is that because this is external to the SharePoint or the system it has no access to the DOM/Connection so it is easier to deploy and provide access to and the End users can install add-ins on NoScript sites.
But using the SPFx we can create the web parts which can be added to the page as an app, and just like an app all the processing is done in the background without many hassles of the authentication as it will use the user’s context to execute which makes it secure in its own ways.
The SharePoint Framework has been introduced by Microsoft to allow users customizability and more control over the efficiency and the SharePoint environment that they use. This framework also can overcome all the shortcomings of the previous option that Microsoft introduced to create and add custom solutions to the SharePoint. We can use the SharePoint Framework (SPFx) to our benefit and the benefits of our users.