SharePoint Framework was first released for client side web parts. This was just the starting of this journey. It has a great future and will start to provide addition features which are listed below. Lets discuss about future of SharePoint Framework and its support:
What is SharePoint Framework (SPFx)
Future prospects of SharePoint Framework (SPFx)
Required tools and libraries for SharePoint Framework (SPFx) development
Setup Microsoft 365 tenant for SharePoint Framework development
Setup SharePoint Framework client side web part development environment
Build SharePoint client side web part using SharePoint Framework (SPFx) – I
Build SharePoint client side web part using SharePoint Framework (SPFx) – II
Build SharePoint client side web part using SharePoint Framework (SPFx) – III
How to Debug SharePoint Framework Solutions in Visual Studio Code
What is the Developers Point of View on SharePoint Framework
What is Required Toolchain for SharePoint Framework
How to Integrate gulp tasks with SharePoint Framework Toolchain
How to Provision SharePoint assets with solution packages
How to Upgrade SharePoint Framework client side solutions in SharePoint Online
SharePoint Framework has already started support for On-Premises SharePoint applications which is similar to the features in SharePoint Online. It is targeting all SharePoint versions.
Client side web parts and add-ins
It helps to build more modern and complex scenarios. It also supports for building Add-ins for SharePoint with SharePoint Framework.
It replaces custom actions and JSLinks with SharePoint Framework-based extensions, use site collection App Catalog and work with NoScript via tenant app catalog.
Full page Apps
SharePoint Framework apps are rendered in full page mode rather than as in client side web parts. It works at list, page and mobile level customization.
Dev certificate issue with Chrome (v58-)
In case of using Google Chrome as development browser, there may be challenges while certificate validation. It is because Chrome has changed its algorithm to validate certificates starting from its version 58.
You may see error “Your connection in not private”.
You should update your Yeoman template package. That’s why, you need to delete @microsoft/gulp-core-build-serve folder and run npm install to get the updated package. Therefore, you need to execute untrust-dev-cert and trust-dev-cert commands in your machine to address the certification creation logic issue.
Thank you for reading!
Hope you liked this article!
Please Follow, Like & Share to get updated with latest posts.
We will see mandatory tools and libraries for SharePoint Framework (SPFx) in next article.
Hope you enjoyed reading it.
Please don't forget to Share, Follow and Like to get updated with latest posts.
It gives me motivation to share more knowledge with you.
Project Management Professional (PMP) and Microsoft certified, motivated, energetic and accomplished Project Manager / Architect with 15+ years of work experience in Management, Architecture, Analytics, Development and Maintenance. I have been fortunate to be a part of over 25+ .Net / SharePoint projects delivery with various companies across different industry sectors. This has provided me a valuable insight and experience especially in successful implementation of SharePoint based solutions.
My experience in Web application implementation includes technology strategy and road-map definition, business and technical requirements identification, governance, platform architecture, solution design, configuration, development, quality assurance, training, post-production support, team lead and overall project delivery along with project management.
Satyendra Mishra holds a B.Tech. in Computer Science & Engineering and PG Diploma in Advance Computing from Center for Development and Advance Computing, Pune, India. He is also a certified Project Management Professional (PMP).
I love to share Project Management Tips and Tricks by writing Blogs in the Project Management India Community. I have written around 300+ articles in the Project Management, .Net, SharePoint and related client side technologies.
5 thoughts on “What is the future of SharePoint Framework”