The good thing about the SharePoint Framework is that it doesn't replace or deprecate any existing SharePoint investments. On the contrary, it complements them, and here at Rencore, we think that the most powerful solutions will be a combination of the SharePoint Framework for the UX and the existing SharePoint Add-in model for executing complex business logic.
SharePoint development before– complicated but within boundaries
Previously, developing for SharePoint was reserved for Visual Studio on Windows. Developers were majorly using C#, and communicating with SharePoint was done using SharePoint's server API and now using JSOM, REST, or CSOM. Even though SharePoint development was based on a proprietary model and required a sufficient amount of particular information.
It was the same for a few years, and over time best practices came to help developers customize SharePoint. in spite of its complexity and high costs, there is a vast requirement for customizing SharePoint, sometimes above what's supported and recommended by Microsoft.
To help customers control their SharePoint environment and verify that all customizations as required to organizational rules, they created SPCAF. Using over 800 different rules, we transformed market standards and best practices into a sophisticated analysis that integrates with the application lifecycle management of SharePoint customizations. It automatically verifies that customizations as required to all rules – both those that we provide and those that our customers specifically want for their organization – and it does that on every step of the customization's lifecycle: from a development workstation to release processes and centralized build. SPCAF teaches developers and helps them verify that their work meets the organization's quality bar. Simultaneously, SPCAF is a part of the build and release management systems to ensure that the only solutions that are more preferred are released. Thanks to SPCAF, adhere to organizational rules is no afterthought and can be accomplished without minimizing the developer's performance.
Finding a problem is only the first part of what SPCAF does.along with its extensive set of rules. SPCAF also guides what the best practices are required for fixing a particular problem. You could assume of SPCAF as the quality assurance assistant for your organization, and it precisely sets of guidance and rules that make it invaluable for every organization.