While we were developing on On-Premise (2007/2010) we were
developing the Solutions (WSP). WSP contains the sets of Features, Site Definitions,
assemblies etc written in c # and that get deployed on SharePoint Servers.
After that Microsoft introduced AddIns. SharePoint Addins
avoided the Server deployments and change the deployment pattern. Prevented
these solutions from running physically on the Web Front End servers.
After that Microsoft has introduced SharePoint Framework
(SPFx). A complete client side development and these webparts can run in the
context of page it means no Iframe which was the pain area with SharePoint
addins, no cross domain calls on your webparts
The New Tool Chain of SharePoint FrameWork.
 |
| Tool Chain Info graphics which will tell what replaced what |
This is the development server. Earlier you ware familiar with
IIS and Microsoft Visual Studio. Now you just need to install this and forget
IIS and VS. You do not need to touch the node.js after installing it.
This is the replacement of your NUGET. Which you were familiar
with Visual Studio while installing the things using nugget package.
A Scaffolding tool for development projects,
which helps us kick-start new projects, and prescribes best practices and
tools to help you stay productive. SharePoint client-side development tools
include a Yeoman generator for creating new web parts. The generator provides
common build tools, common boilerplate code, and a common playground web site
to host web parts for testing.
It’s Same like as you were earlier doing File à New à Project à Select Template in
Visual studio.
A task and build manager that provides automation for build
tasks, which is like MS build.
TypeScript, React, Knockoout and many other languages can be
used to develop the Web part in SharePoint Framework.
No comments:
Post a Comment